Re: ASTs

One thing that you'll definitely run into is some compiler-only syntax for
fragments:

  #{ make(<suffixed-macro-descriptor>,
          word-class: ?word-class,
          suffix:     "-definer",
          expander-function: ?expander-name) }

These create fragments and are used in many places within dfmc, mainly when
generating code, but also when expanding definitions.

There is also a macro-case which lets you match patterns and are useful for
crossing the bridge between values and fragments.

I'm not sure who actually understands this stuff ... I only know bits and
pieces of it from reading code.

 - Bruce


On Thu, Jan 17, 2013 at 3:00 PM, mikel evins <[email protected]> wrote:

>
> On Jan 17, 2013, at 1:53 AM, Bruce Mitchener wrote:
>
> >
> > On Thu, Jan 17, 2013 at 2:41 PM, mikel evins <[email protected]> wrote:
> > Obviously, the goal is to rurn the Bard sketch into a real
> implementation of a readtable-based reader that generates ASTs in
> OpenDylan's native format. The obvious question to ask is, "where can I
> find out more about the native format of OpenDylan's ASTs?"
> >
> > A good place to start is the Hacker's Guide:
> >
> >
> http://opendylan.org/documentation/hacker-guide/compiler-internals.html#dfmc-reader
> >
> > This document needs a lot of improvement, but it might be a useful
> start...
>
> Great! Thanks.
> _______________________________________________
> hackers mailing list
> [email protected]
> https://lists.opendylan.org/mailman/listinfo/hackers
>

_______________________________________________
hackers mailing list
[email protected]
https://lists.opendylan.org/mailman/listinfo/hackers