> > The big difference in my mind is that I can think of what the resulting JS > > will be almost perfectly when I read or write CS. My mind isn't good enough > > to do that with streamline.
If you are not comfortable with the callback rewriting done by streamline, you have the option of running it in "fibers" mode. In this mode, the generated code is very similar to the source (and, unlike CS today, line numbers and comments are preserved). For example, take a look at: https://github.com/Sage/streamlinejs/blob/master/lib/compiler/compile--fibers.js https://github.com/Sage/streamlinejs/blob/master/lib/compiler/compile_.js As Jann mentions, this is a general issue with compilers. At some point, you just have to *trust* the compiler and the people behind it. V8, for example, is applying all sorts of amazing tricks to our code. I never felt the need to look at the instructions that it generates. I just trust it, and, if one day I find something odd, I'll file a bug report and I have confidence that the V8 gurus will fix it. Same thing with CS, and with streamline. Bruno -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
