What can you do to get yourself up to speed? That's a good question. Here are some suggestions.
- Read the Apocalypses and Exegesises.
- Learn how to write and understand a grammar (in the computer sense--something you'd feed to lex and yacc). Grammars make writing compilers a lot easier.
- General background reading on parsing is good
- Intro CS texts on compiler generation are useful. (Though skip the Dragon book, it's not that good)
- Practice! Write parsers for simple stuff, play with Parse::RecDescent, Parse::YAPP, and Parse::Nibbler, twiddle around.
- Look at the grammars for other languages. Perl and Ruby both have grammars that ship with them. (Though I'm not sure that'll help or hurt...)
- Size up your skills and decide what you realistically are up to. We need folks that can do all sorts of things, not just write compilers, so any and all help's useful.
-
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.
|