Re: macros, procedure->macro

[Rob Browning]

Dirk Herrmann <address@hidden> writes:

> That is, if we plan to split up syntax transformation,
> compilation/memoization and execution, we could not remove "acros"
> and "macros" from the execution, since they may behave differently
> every time the same code is executed.
>
> I therefore strongly suggest to get rid of "acros" and "macros".  As
> a first step, I suggest to get rid of "macros" and their
> scheme-level representative procedure->macro

Presuming I'm remembering my most recent look in to this stuff
correctly (about 6 mos ago), I believe you're right, but Marius may
have further comments.

> If all results are positive, I will go ahead and remove the support
> for "macros" from guile.  After that, I will take a close look at "acros"
> and we will play a similar game with "acros" again...

It may also be important to consider pssyntax (i.e. syntax-case,
etc.).  In the end I'd like to have one unified macro system whose
behavior and interactions with the rest of guile are very clear.

Thanks

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C  64AE 78FE E5FE F0CB A0AD