Have an idea, suggestion, or something that doesn’t work as expected in InterSystems products or services? Share it here on the InterSystems Ideas Portal.
The Ideas Portal is where community members can propose improvements, report bugs, and help influence the product roadmap across InterSystems products and the overall developer experience. 22% of submitted ideas are implemented by InterSystems or members of the Developer Community.
💡 Ideas and bugs are both welcome, no matter how big or small. You can submit feature requests, usability improvements, workflow suggestions, and bug reports. Whether you’re an experienced expert or just getting started, your fresh perspective is valuable.
🛠️ About bugs and fixes. If you have access to InterSystems WRC, please submit bugs there for immediate action. Bug reports submitted through the Ideas Portal are reviewed and tracked, but do not guarantee immediate resolution.
Start by sharing what could be better - the community and our teams will help take it from there.
I agree local class macros is definitely a missing component. Especially as modifying and compiling a include file does not trigger compilation if dependent classes.
Total agree!
We have transient properties
We have parameterstatt are local to the class.
Local Macros are definitely a missing components.
For pure values we may use Parameters, computed properties.
BUT: a Macro can and mostly does reflect a piece of static code.
all ZLANG+ stuff goes that direction. But this is not LOCAL.
The concept of macros goes back to early Assembler Languages,
to define a static sequence of commands. A key success factor at that time.
The concept war taken into .MAC code in COS.
I have no imagination why it filed to be available also in Classes .