Skip to main content
9 events
when toggle format what by license comment
Sep 9, 2015 at 23:42 history edited Nikolay Gromov CC BY-SA 3.0
added 5 characters in body
Sep 9, 2015 at 23:42 comment added Nikolay Gromov You just type expression and on the way to the kernel it gets replaced by this monster and then back on the way back. The same as with any other 2D expression. Anyway I edited "Most recommended" as I personally would rather do a[1] just because that's faster.
Sep 9, 2015 at 22:48 comment added Albert Retey That's what I tried to express: there is much going on under the hood and things become more complicated than they need to. My experience is that code doesn't become more reliable if it is more complicated then necessary. I think it is absolutely OK to use the Notation package if you have need for it but just wouldn't call it "most recommended" for all use cases...
Sep 9, 2015 at 17:01 comment added Nikolay Gromov This symbol also have a long alias: a\[UnderBracket]Subscript\[UnderBracket]1 which has no boxes
Sep 9, 2015 at 16:54 comment added Albert Retey Well, I think it depends on the frontend and the functionality to turn boxes into expressions. Messing with these makes me feel uncomfortable as it makes code too difficult to understand for me, especially when errors occur. But true, it might well work reliable if used correctly and in the scope it is meant to...
Sep 9, 2015 at 16:48 comment added Nikolay Gromov This is quite reliable. Even though I personally prefer 1D notations. This could considerably increase readability of the code.
Sep 9, 2015 at 16:38 comment added Albert Retey I would argue that "most recommended" is limited to cases where presentation is more important than code reliability and reusability...
Sep 9, 2015 at 15:32 history edited MarcoB CC BY-SA 3.0
Formatted code in text
Sep 9, 2015 at 14:05 history answered Nikolay Gromov CC BY-SA 3.0