Slash Boxes
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • I welcome AS's effort in doing this, as in many people's eyes it legitimises Perl on Win32 (if not in general).

    Unfortunately, I think the MS IDE is particularly poor at being anything like a professional development environment - I spend plenty of time trying to wean my C++ developers off the VC++ IDE if only to open their eyes to how there are better ways to do things, integrate with other tools, use open rather than closed toolsets, to be aware of what they do rather than rely on wizards and similar... in short to spend more time making their intent clear in the code they write (which is what other developers have to read), rather than making their intent clear to an IDE which takes delight in doing what they want, but recording only the obscure end result. Sort of like a compiler that writes the object file but deletes the source code...

    Of course, if AS can take this a chance to turn Perl into a competitor in the VB market (ie simple drag'n'drop of GUI design and hooking up handlers) then I think Perl could revolutionise GUI prototyping and "small-GUI" apps in the same way that it made such a huge impact on the "text-and-file manipulation" area. I recently prototyped a custom 3 tier global system in perl, but the (thick) client had to be done in VB to get all the work done in a reasonable timescale (using PerlCOM to let VB call the Perl communications layer) - if I could have written the GUI mock-up in Perl too I think I could have done a much better prototype much quicker, but the Tk and Win32::GUI modules need some visual tools...