Hi,
Would it not be a good idea to remove the macro keyword? It doesn't seem
like there's anything happening with the AST macros idea anyway, and
it's an identifier that I actually find myself wanting to use
occasionally...
Regards,
Alex

Hi,
Would it not be a good idea to remove the macro keyword? It doesn't seem
like there's anything happening with the AST macros idea anyway, and
it's an identifier that I actually find myself wanting to use
occasionally...
Regards,
Alex

Any input on this? Especially from people hacking on DMD?
Reserving a common word like this for no purpose is not very reasonable
IMO...
Regards,
Alex

Hi,
=20
Would it not be a good idea to remove the macro keyword? It doesn't=

like there's anything happening with the AST macros idea anyway, an=

it's an identifier that I actually find myself wanting to use
occasionally...
=20
Regards,
Alex

Any input on this? Especially from people hacking on DMD?
=20
Reserving a common word like this for no purpose is not very reasonab=

IMO...

At this point, I think that it is the way that it is, and it's going to=
stay=20
that way - if nothing else because there's every possibility that a new=
=20
feature will be added at some point in the future which uses the macro=20=
keyword. If we do add such a feature, it probably won't be until D3, bu=
t if we=20
have the macro keyword in D2, then there's a greater chance of being ab=
le to=20
add such a feature in a backwards compatible manner into D2.
Removing the keyword now is just going to cause problems later if we ev=
er want=20
it as a keyword again.
- Jonathan M Davis