#63 #define equivalent - MWorks Core Components

Type	To find
responsible:me	tickets assigned to you
tagged:"@high"	tickets tagged @high
milestone:next	tickets in the upcoming milestone
state:invalid	tickets with the state invalid
created:"last week"	tickets created last week
sort:number, importance, updated	tickets sorted by #, importance or updated
Combine keywords for powerful searching.
Use advanced searching »

#63 ✓hold

#define equivalent

Reported by David Cox | October 18th, 2010 @ 03:22 PM

I've heard numerous requests over the years for the equivalent of a #define in MW.

Such a construct would:

not clutter up the variables window, etc.
function in places where variables cannot (e.g. the range in a replicator; as an aside we could also allow variables function in this way with their default values, those this opens up some potential confusion about what replicators are and when they are evaluated).
possibly extend beyond just values (e.g. function names, operators, etc.)

Some thought / debate should probably go into what scope/scale such a thing would take (e.g. operates just in "expression" contexts? just scalar values? a full macro preprocessor? etc. etc.).

Comments and changes to this ticket

Christopher Stawarz April 8th, 2011 @ 10:49 AM
- State changed from “new” to “open”
[bulk edit]
Christopher Stawarz July 20th, 2012 @ 02:13 PM
Assigned to Tender discussion #68.
Christopher Stawarz September 8th, 2017 @ 10:49 AM
- State changed from “open” to “hold”
MWEL supports macros

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.