Searching \ for '[PIC]: Programming in C.' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: www.piclist.com/techref/microchip/devprogs.htm?key=programming
Search entire site for: 'Programming in C.'.

Exact match. Not showing close matches.
PICList Thread
'[PIC]: Programming in C.'
2000\10\06@073959 by Michael Rigby-Jones

flavicon
face
> -----Original Message-----
> From: Andrew Kunz [SMTP:spam_OUTakunzTakeThisOuTspamTDIPOWER.COM]
> Sent: Friday, October 06, 2000 12:29 PM
> To:   .....PICLISTKILLspamspam@spam@MITVMA.MIT.EDU
> Subject:      Re: [PIC]
>
> Andy,
>
> Download the PICLITE compiler from http://www.htsoft.com
>
> It is great as a tool to learn C.  That, and a thin book.
>
> If you know BASIC, then the concepts and a lot of function names will make
> sense
> to you.
>
> Andy
>
>
>
Although strings will have you pulling your hiar out :o)

I learnt C by using a DOS Compiler (actually Microsoft Quick C but Borland
Turbo C is good, and HiTech have their own freeware Dos compiler), when I
was into the old graphic demo scene.  Books are great as a reference, but
nothing can beat actually getting stuck in and compiling your own programs.
I'd be tempted to start with a DOS compiler as you have no need for a target
board, and debugging is usualy much easier.  Start with the "Hello world"
stuff until you get a feel for the syntax, the idea of include files etc.
then you are ready to play with more advanced ideas such as pointers, data
structures etc.

Be a little carefull with pointers, my last boss somehow managed to create a
bunch of undeleteable directories on his hard drive after a "wild" pointer
was let loose in one of his programs!

Debugging C programs can be a very frustrating experience, simply leaving
out a semi-colon somewhere in your program will produce an enormous list of
apparently unrelated errors when you try to compile.  All stuff you'll learn
with some experince though.

Regards

Mike






{Quote hidden}

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.


2000\10\06@075819 by Alan B. Pearce

face picon face
>Debugging C programs can be a very frustrating experience, simply leaving
>out a semi-colon somewhere in your program will produce an enormous list of
>apparently unrelated errors when you try to compile.  All stuff you'll learn
>with some experince though.

If there is a preprocessor that produces output you can look at, it is often well worth looking at the output from it when getting this sort of error, as all the comments get removed, and you can see just what the compiler sees as input. Can be quite revealing.

I do not know if any of the PIC C implementations will do this for you.

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.


2000\10\06@081239 by D Lloyd

flavicon
face
part 1 1875 bytes content-type:text/plain; charset=us-ascii
Hi,

Pacific C is a nice, free DOS compiler but suffers from pants debugging (if
you know assembler, though, you can see what is going on). I learnt from
using the superior debug environment of MS Visual Studio (better than
Borland, IMO) - you can see precisely what is going on in the source and
the error/warning messages are relatively extensive - essential for
starting out. Not to mention, a reasonable dollop of help complete with
code examples. At least this way, you can build the data/application level
code on a PC (with appropriate stubs) to get an idea of it working, then
make a go of porting to your microcontroller.

However, MSVC isnt cheap. You get what you pay for.

Regards,
Dan




(Embedded     "Alan B. Pearce" <A.B.Pearcespamspam_OUTRL.AC.UK>spamspam_OUTMITVMA.MIT.EDU>> image moved   06/10/2000 12:56
to file:
pic11585.pcx)





Please respond to pic microcontroller discussion list
     <
@spam@PICLISTKILLspamspamMITVMA.MIT.EDU>
Sent by:  pic microcontroller discussion list <KILLspamPICLISTKILLspamspamMITVMA.MIT.EDU>


To:   RemoveMEPICLISTTakeThisOuTspamMITVMA.MIT.EDU
cc:
Subject:  Re: [PIC]: Programming in C.

Security Level:?         Internal


>Debugging C programs can be a very frustrating experience, simply leaving
>out a semi-colon somewhere in your program will produce an enormous list
of
>apparently unrelated errors when you try to compile.  All stuff you'll
learn
>with some experince though.

If there is a preprocessor that produces output you can look at, it is
often well worth looking at the output from it when getting this sort of
error, as all the comments get removed, and you can see just what the
compiler sees as input. Can be quite revealing.

I do not know if any of the PIC C implementations will do this for you.

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.






part 2 165 bytes content-type:application/octet-stream; (decode)

part 3 131 bytes
--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.


2000\10\06@083948 by Andy Howard

picon face
> From: "Michael Rigby-Jones" <spamBeGonemrjonesspamBeGonespamNORTELNETWORKS.COM>> > -----Original
Message-----
> > From: Andrew Kunz [SMTP:TakeThisOuTakunzEraseMEspamspam_OUTTDIPOWER.COM]

> > Andy,
> > Download the PICLITE compiler from http://www.htsoft.com
> > It is great as a tool to learn C.  That, and a thin book.
> > If you know BASIC, then the concepts and a lot of function names will
make
> > sense
> > to you.
> >
> Although strings will have you pulling your hiar out :o)

I'm losing it fast enough without any external help these days. :>

> I learnt C by using a DOS Compiler (actually Microsoft Quick C but Borland
> Turbo C is good, and HiTech have their own freeware Dos compiler), when I
> was into the old graphic demo scene.  Books are great as a reference, but
> nothing can beat actually getting stuck in and compiling your own
programs.
> I'd be tempted to start with a DOS compiler as you have no need for a
target
> board, and debugging is usualy much easier.  Start with the "Hello world"
> stuff until you get a feel for the syntax, the idea of include files etc.
> then you are ready to play with more advanced ideas such as pointers, data
> structures etc.
> Be a little carefull with pointers, my last boss somehow managed to create
a
> bunch of undeleteable directories on his hard drive after a "wild" pointer
> was let loose in one of his programs!

Hehehe. It's always better when it happens to the boss.

> Debugging C programs can be a very frustrating experience, simply leaving
> out a semi-colon somewhere in your program will produce an enormous list
of
> apparently unrelated errors when you try to compile.  All stuff you'll
learn
> with some experince though.

Ta for the tips Mike, looks like this could be a long-term project then.

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.


More... (looser matching)
- Last day of these posts
- In 2000 , 2001 only
- Today
- New search...