Re: What's the status of modules and macros?

[Marius Vollmer]

Michael Livshin <address@hidden> writes:

> Marius Vollmer <address@hidden> writes:
> 
> > I just realized that we don't need to specially tag gloc pointers when
> > they point to variables since variables can be identified already on
> > their own (while vcells can't).  That would significantly cleanup the
> > gloc/struct tag clash magic (which is something that you probably
> > don't want to know about) since we can use the gloc tag for structs
> > exlcusively then.
> 
> you don't even realize how cool that would be!  well, I guess you do. ;)

I do... 8-)

> > Right now it would happen at run-time, at the first hit.
> > Conceptually, I'd say it should happen at load time, when a body of
> > code is massaged into the Guile run-time image.
> 
> I think "link time" would describe this pretty well too -- you resolve
> references to globally visible entities.

Yes, but isn't `load time' the same as `link time' in our setup?

> just so I understand: you take a combination of two things that are
> unportable by definition (defmacros & modules (well, defmacros are
> kind of semi-standard, but still)), and you are worried that the
> result will be unportable?  I say there's not a lot to worry about.

No, I'm not really worried.