Re: Pointers to "why C behaves like that ?"

+ [I don't see a useful difference between a system that requires that you
+ declare everything, vs. one that doesn't but produces undeclared variable
+ warnings that the programmer treats like error messages. -John]


thp@cs.ucr.edu wrote:
> Some of my students are Pythonistas. They insist that the lack of
> such assistance from the compiler in detecting typos has never been an
> issue. (I wouldn't know.)


Do these students have *serious* programming experience? Are their
programs large enough that long variable/function/module names make
sense? If the answer to either question is "no", I'd consider their
experience to be unrelated to everyday practice ;-)


Regards,
Joachim

Return to the comp.compilers page.
Search the comp.compilers archives again.