On Tue, 2006-07-18 at 02:48 -0700, Erick Tryzelaar wrote:
> > * For some reason I do not understand, you need this:
> >
> > macro var break = { goto lab3; };
>
> Another bug on the list! :)
> > What I don't understand at the moment is why this works
> > with a macro var, but NOT a macro val.
> And another!
Eh? That's one possible bug -- val doesn't work, var does.
It may not be a bug -- not sure.
The need for a val/var to be an expression isn't a bug,
although it is a kind of design problem.
Basically expressions, statements and statement lists
are the three types the macro processor can work with,
but they're handled very inconsistently.
The macro processor treats tuples as lists, and there
is some hackery to wrap up a statement into an expression.
The overall design is a bit messy.. macro processors
are intrinsically messy!
--
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Felix-language mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/felix-language
