[prev] [thread] [next] [lurker] [Date index for 2005/04/10]
On Sat, Apr 09, 2005 at 04:50:10PM -0700, Michael G Schwern wrote: > > That's because in "C" it's preprocessed before the compiler sees it. > > > > Run your javascript through the preprocessor. > > > > If that's too hard, then hide it, make it automatic, like it is in C. It's > > a function of the hosting environment, not the language. Something I forgot... preprocessing IS part of the C language. Ok, let's split hairs here. Preprocessing is part of the C *standard* which is much more useful to talk about than the C *language* which does not even include a way to print. This exposes why my using a pre-processor does not solve the problem of a language standard not having an include method, be it at run-time via eval as in dynamic languages or at compile-time via a pre-processor in C. Its part of the C standard. It is not part of the Javascript standard. This means that *locally* I can slap together whatever pre-processor include system I want for Javascript and use it but I cannot ship code which uses it because it won't run anywhere else. Its not standardized. I have to ship the post-processed spaghetti. And if anyone's ever looked at post-processed C code from even a simple program... eww. Not getting any useful patches against that. You can't ship nice, neat, reusable modules. You can't have a CJSAN. Modular programming is crippled. How far would C have gotten if #include was not standardized? Not very far. A defacto standard would have emerged PDQ.There's stuff above here
Generated at 12:00 on 12 Apr 2005 by mariachi 0.52