[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: dylan revival



> OK, maybe I'm thick, but I don't see how Dylan macros are a problem.  In
> d2c they are completely dealt with in the parsing stage, and this runs
> pretty damn fast -- certainly fast enough that we'll need to make all of
> library loading, library dumping, optimization, and C code generation at
> least an order of magnitude faster than they are at present before we'll
> even notice parsing/macro expansion as a bottleneck.
> 
> Maybe the implementation is complex.  Who cares?  It's written.  Even if
> someone develops a macroless Dylan compiler, it'd be a pretty small
> effort to modify d2c to dump out demacrofied Dylan source code that
> could be fed in to this hypothetical new compiler.

I was referring both to difficulty of implementation and difficulty of
comprehension and use. It never occurred to me to think that parsing
performance could be a problem; the days of CPUs that slow are long past ;-)


-- 
Scott Ribe
scott_ribe@killerbytes.com
http://www.killerbytes.com/
(303) 665-7007 voice