What would a macro system look like in squeak?  could you effectively browse
implementors and senders of the macro symbols?

note that in this case i don't have a technical issue with the compiler hack
because they are turned into msg sends.  Assignment and return are syntax
which I would _love_ to see become msg sends.  this could be done with
macros, couldn't it?  if the lookup fails for those selectors, we could
fallback to the vm bytecode handler.   assignment could expand to
'thisContext assign: value to: variableBindingOrSymbol' and return could
expand to 'thisContext return: value'.  then jit it.

rob

From: "Stephane Ducasse" <ducasse at iam.unibe.ch>

But then can you explain me as a new guy where I can find the
definition of {}
because I can find ifTrue:, do:.... but {} is hardcoded in the compiler
as the other constructs.
So may be it would be better to have a way to declare new construct
than hacking them
in the compiler. At least we could present it in a non ad-hoc fashion.

Note that this may be a bad solution because programmers are like gaz,
they tends
to use of the features proposed. So I'm sure that in no time we would
end up in a mess.