Yes, a FOO-to-Parrot compiler is always possible. There are, if I counted correctly, at least 10 languages targeting Parrot right now, and Perl isn't one of them. (Though Python is ...)

But, the hype about MS ending free support for VB6 ... whatever. It's not like my VB code is going to suddenly stop working. Not to mention that the VB interpreter is still going to be part of WinXP, WinServer2k3, and Win2kPro. Oh - and .Net (which means it's part of Mono, which is F/OSS). It just isn't going to be part of Longhorn.

As for transitioning a product from language X to language Y ... the basic rules apply.

Not to mention that transitioning from VB (which is extremely OO) to Perl (which isn't) is going to be problematic. Transitioning from VB (which is crappily OO) to Ruby (which isn't) is also going to be problematic. Transitioning from anything to PHP (which is a toy) is dumb. (I don't know Python well enough to make stupid comments about it.)

Frankly, I'd rewrite VB applications in Javascript (which is actually a pleasant language once you get past the browser incompatibilities) and go from there. At least, you still have the same graphical interface you're used to.

Being right, does not endow the right to be rude; politeness costs nothing.
Being unknowing, is not the same as being stupid.
Expressing a contrary opinion, whether to the individual or the group, is more often a sign of deeper thought than of cantankerous belligerence.
Do not mistake your goals as the only goals; your opinion as the only opinion; your confidence as correctness. Saying you know better is not the same as explaining you know better.

In reply to Re: Visual Basic to Perl transition by dragonchild
in thread Visual Basic to Perl transition by szabgab

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.