Re: [PIC] Learning C

"...trying to make digital files uncopyable is like trying to make water not wet."
Bruce Schneier


Sent with Proton Mail secure email.

On Sunday, November 10th, 2024 at 3:26 PM, Charles Craft <[email protected]> wrote:

> IM(not so)HO, to be good at C you need to think in C.
> 
> https://en.wikipedia.org/wiki/The_C_Programming_Language
> 
> Start with K&R.
> 
> -----Original Message-----
> From: Microcontroller discussion list - Public. [email protected]
> 
> Sent: Nov 10, 2024 12:34 PM
> To: Microcontroller discussion list - Public. [email protected]
> 
> Subject: [PIC] Learning C
> 
> Although I enjoy programming in Assembler, the fact that so many libraries
> abd code examples are in C I think that the time has come for me to learn
> that language.
> 
> Any advice on how to do that would be welcomed, be it a book or online
> resources.
> I am a competent programmer having programmed in with Forth, Fortran.
> \Pascal, Visual basic
> __________________________________________
> David C Brown

In some ways both views are useful and correct.  I always find it best to analyze/think about things from multiple theoretical perspectives, and different branches of knowledge/reasoning.  The more ways you understand something and how it interacts the better.  If doing digital design it's essential to remember that it's really analog and the "digital" is a coarser (and hence simpler) view of things.  Each way is useful, each way has problems depending on what exactly you are trying to do and what happens on the test bench.  This is extremely important when trying to debug or repair things, new design or old piece of gear/code.  Also often essential for improving them.