Well, my assumption was that I would start off by producing some kind of source
code on disk that is the same kind as that which defines Rakudo, which your
existing toolchain could then compile and execute. Similar to how my current
implementation actually produces equivalent Perl 5 source code which then runs
as normal Perl 5 code. When I say bootstrapped I mean that the code which
produces the Perl 5 code first, and whatever speaks QAST later, is written in
Muldis D. Anyway, I don't think there's any confusion here. -- Darren Duncan
On 2013.02.02 6:15 PM, Matthew Wilson wrote:
Right, but (sorry if this is already clear) there's no textual QAST language;
you currently must be running in NQP to create the node objects. If you wanted
to use a Perl5-bootstrapped Muldis D to produce QAST, you could write it to some
serialization on disk, then you would need to deserialize that tree in NQP code
and use the regular compiler toolchain there.
On Sat, Feb 2, 2013 at 6:05 PM, Darren Duncan <dar...@darrenduncan.net
<mailto:dar...@darrenduncan.net>> wrote:
Okay, I understand, I would target QAST. So once I've implemented over Perl
5, and bootstrapped where possible, I'll work on targeting QAST. Thank you.
-- Darren Duncan
On 2013.02.02 4:29 PM, Matthew Wilson wrote:
QAST is the protocol rakudo and NQP use to send abstract syntax trees to
the VM-specific compiler. PIRT is the target for parrot, and JAST is
the
target for nqp-jvm. You can view its source in nqp's source under
src/QAST, as well as note src/NQP/Actions.pm, which generates the QAST
nodes while parsing NQP code.
On Sat, Feb 2, 2013 at 4:26 PM, Matthew Wilson <diakop...@gmail.com
<mailto:diakop...@gmail.com>> wrote:
I'm sorry; I was just filling out what the last letter in the
acronym QAST
is. Search for QAST instead.
On Sat, Feb 2, 2013 at 4:21 PM, yary <not....@gmail.com
<mailto:not....@gmail.com>> wrote:
This doesn't happen very often. Google tells me
Your search - *QASTree nqp* - did not match any documents.
where does one read more about this QAStree?
