Replies: 2 comments 3 replies
-
Place the private procedures inside the global one. |
Beta Was this translation helpful? Give feedback.
-
The main problem I do have with private code is that it is close to impossible to modify be 3rd party programmers. So everything basically is hardcoded and changing something will need to overwrite the whole global code. Debugging private code also is a pain, since it cannot be easily reached, except if it is \imported. -- But imo managing imported content also is painful within TW editors. There is no fast way to open So for my code I try to avoid it. Having well defined procedure and function names helps to avoid naming clashes and it forces me to really think about "self documenting" names. Which imo is an advantage for maintenance. Just some thoughts -m |
Beta Was this translation helpful? Give feedback.
-
Whan you have a tiddler contains procedures/functions/macros and tagged with$:/tags/Global or $ :/tags/Macros every routine is global. Sometimes you want sub procedures/functions/macros which are used by other procedures/functions/macros. In this case you like to have private procedures/functions/macros.
One way is: to use NOT global procedures/functions/macros are defined in separate tiddlers and then import them inside procedures/functions/macros.
My idea is: can we use double underscore or similar format in the name of such procedures/functions/macros and make them private?
Beta Was this translation helpful? Give feedback.
All reactions