In article <l8so4d$snu$2...@reader1.panix.com>, Grant Edwards <invalid@invalid.invalid> wrote:
> On 2013-12-18, Roy Smith <r...@panix.com> wrote: > > In article <l8pvsl$60h$1...@reader1.panix.com>, > > Grant Edwards <invalid@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". -- https://mail.python.org/mailman/listinfo/python-list
