What Parrot will allow is the creation of simple domain-specific languages.
Not just domain specific languages, but transition paths from dead-end languages as well. You write a compiler for the old language that targets parrot and rewrite the runtime library code for it, and then you're in a position to start migrating. That's what I'm doing now for work.
Granted, this isn't the right answer in all cases--rewriting a runtime library to maintain compatibility can be a major undertaking. In many cases, though, it's easier to write a new compiler for an existing code base that targets a back end with more potential than it is to port the entire code base to a new language. (Writing compilers and their associated runtimes is a lot of work. Rewriting full application systems are often significantly more work, though, with more risk and expense)
I'll put the ObPlug here for part one of an article I wrote for OnLamp about this, but targeting parrot's not that tough.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|