#1233: McLachlan should not define one-character variables ------------------------------------+--------------------------------------- Reporter: knarf | Owner: Type: enhancement | Status: new Priority: optional | Milestone: Component: EinsteinToolkit thorn | Version: development version Resolution: | Keywords: ------------------------------------+--------------------------------------- Changes (by knarf):
* priority: minor => optional
Comment:
In my case I now had to adapt an existing thorn which I wanted to have access to some (but not all) McLachlan variables. This is now done, but the general problem remains.
Luckly McLachlan doesn't define K, as k is an often used temporary variable name - exactly what I had in my case, just with 'A' and 'B'.
I agree that longer names can be cumbersome. The would definitely make expressions 'longer'. Also - we might actually 'get away' with most of this once the READS/WRITES mechanism is implemented fully and not everything is imported through inheritance automatically.