On Fri, Jan 07, 2005 at 05:11:18PM +0100, Sven Schubert wrote:
> Hi all,
>
> I've been reading the internals list for a while more
> or less regularly and as this is me first post, it is
> about time, that I introduce myself:
>
> My name is Sven Schubert, I am studying information
> systems and business in Germany and currently I'm on
> an exchange program (ERASMUS for fellow euro-zone
> readers) studying a year abroad in Ireland (I.T.
> Carlow).
>
> Now, being here only for the (final) year, I'm not
> only to improve my English big time, but I'll have to
> get into compilers in general and Parrot in
> particular, as my final year project is baptised "A
> Pascal Compiler for Parrot".
>
[snip]
> Any suggestions would be highly welcome.
>
> Thanks a million,
> cheers,
> Sven.
>
The Pascal compiler has been written in Pascal and compiled to Pcode,
a bytecode created for Pascal. I can't find it right how, but it is
somewhare on the net. Or it was a few month ago.
So you can kill two Parrots^Wbirds with one stone by writing a pcode
engine to Parrot. This could be by a metainterpretation of pcode
(slow) or by translating pcode to Parrot bytecode.
I don't say this is necessarily easier than writing a compiler
using current Parrot resources. And you assignement seems to be
to write a compiler, not to get one as a side-effect.
Some info about the pcode: http://www.sciencedaily.com/encyclopedia/ucsd_p_system
--
stef