NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Consistancy
More |
Login
| Reply
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Or is it a BUG?"
"Let's call it an accidental feature. :-)"
--Larry Wall in <6909@jpl-devvax.JPL.NASA.GOV>
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Just goes to show... (Score:2)
The "Do as I say, not as I do" mentality isn't limited to just politicians and high-profile televangelists. Though, to be fair, we should consider that it probably isn't his desk.
It's also worth noting that his ultimate solution in that blog post boils down to an in-house home-brewed language. And, it gets better: it's a dialect of basic that compiles down to VBScript (among other choices). Having had to contort to deal with vendor services written in VB and/or VBScript (*cough*Fandango.com*cough*), I wouldn't be bragging about that. Certainly not on any blog that gets indexed by Google.
--rjray
Reply to This
Re: (Score:1)
His compile-down choice makes sense in his context. He isn’t writing an app that will run on his own servers, he’s writing shrinkwrap software that customers buy and install on their own computers, even though it happens to have a web-based frontend.
Plus, the decision to write that compiler was made because he had a large existing codebase written in pre-.NET VBScript. He needed to future-proof it for the .NET platform and also wanted to target customers on non-MSFT platforms. Between rewrit