Home Original page

Experiences/guidance on teaching Python as a first programming language

Roy Smith roy at panix.com
Wed Dec 18 20:40:53 EST 2013 
In article <l8so4d$snu$2 at reader1.panix.com>,
 Grant Edwards <invalid at invalid.invalid> wrote:

> On 2013-12-18, Roy Smith <roy at panix.com> wrote:
> > In article <l8pvsl$60h$1 at reader1.panix.com>,
> >  Grant Edwards <invalid at invalid.invalid> wrote:
> >
> >> Ideally, you should also have written at least one functioning 
> >> compiler before learning C as well.
> >
> > Why?  I've never written a compiler.  I've written plenty of C.  I don't 
> > see how my lack of compiler writing experience has hindered my ability 
> > to write C.
> 
> I've always felt that there are features in C that don't make a lot of
> sense until you've actually implemented a compiler -- at which point
> it becomes a lot more obvious why some thing are done certain ways.

Example?

I suspect what you mean is, "There are some things that don't make sense 
until you understand computer architecture".
More information about the Python-list mailing list