Hi Rob,

I'm pretty close to you in my views, except that I use VB essentially for the same 
reason I use Perl.  VB owns the user interface, and Perl has the CGI.  I've been 
burned by VB more than a few times by doing work that should have been portable, but 
...  Try using a VB Axtive X control in cross-language development.

One nice thing about Perl is that you can choose your own style.  Many of those 
posting here seem particularly fascinated by tightly packed one-liners.  The language 
supports such constructs quite well.  It also supports my coding style, which tends 
more towards the step-by-step and verbose, pretty well.

It basically comes down to a question of what works for you [and your coworkers].I 
would not want to major OO definition in VB because, to me, it lacks the logical 
crispness of C++.  On the  other hand, for most production projects, I do use VB, 
because it allows very transparent creation of GUI objects, and has a very consistent 
interface for managing their properties.

Perl excels at text-handling.  It seems very well suited to experienced programmers 
who appreciate its packaging of frequently-used routines that would otherwise require 
tedious and uncreative drudge-work to implement.

Rob Richardson wrote:

> David and everybody else,
>
> To me, Perl is a tool to be used when other tools don't fit.  It's
> great to be able to write a program that will run on just about every
> Windows and Unix box ever made, but it's hell trying to use structures
> more complicated than a hash.
>
> Give me Visual Basic first, and then C++.  Perl is a last resort.
>
> Rob
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
> http://mailplus.yahoo.com
>
> --
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to