Re: Guile compilation (getting started playing around)

[Rob Browning]

Marius Vollmer <address@hidden> writes:

> Rob Browning <address@hidden> writes:
> 
> > For example, at first I was presuming that wrt macros, in the long run
> > the hobbit-translator should never even see them, that they should be
> > expanded completely while generating primitive-rep, but will that
> > actually work?
> 
> I think so.  Why not?

Dunno :> Just figured there might be problems I hadn't thought of
since I'm just getting started thinking about the implications.

> It will lead to errors when *debugging?* is not defined at compile
> time when the macro transformer is executed.

So I guess the only rule here is (which I guess is kinda obvious) that
any variables that are referenced by code inside a define-macro,
defmacro, etc. are going to have to be available at compile-time, but
need not necessarily be available at run-time.

I'm wondering if we'll care about having the ability to define either
compile-time-only or run-time-only variables, though perhaps the
eval-case and eval-when constructs address that.

> We already have this. ;) There is `eval-case' and, in (ice-9 syncase),
> `eval-when'.  They don't recognize `compile-toplevel' yet, of course.
> 
> > I tend to think that whatever solution we choose, being explict rather
> > than trying to devise a clever DWIM system is often best.
> 
> Yep, exactly my opinion.

I'll start playing around once I hear back about the hobbit
copyrights.

Thanks

-- 
Rob Browning <address@hidden> PGP=E80E0D04F521A094 532B97F5D64E3930