Before you pan mini-languages, take a look at the Parrot distribution. Parrot uses preprocessing and mini-languages extensively to make it easier to maintain. Opcodes, the JIT compiler, and PMC (variable) classes are largely written in mini-languages. Documentation is in a mini-language you may have heard of called POD. Configure uses a simple templating mini-language extensively--often to generate Makefiles, another mini-language. Code for Parrot is written in Parrot assembly, but a huge portion of the core is devoted to handling Parrot Intermediate Representation, a mini-language that makes the assembler more usable by offering friendlier syntax and automatically allocating registers.
Used judiciously, mini-languages can save a great deal of time. HTML templating isn't necessarily the right time, but that doesn't mean they're not useful in other situations.
=cut
--Brent Dax
There is no sig.
-
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.
|