Hi Josiah, For a programmer local macro give more flexibility without worrying about overwriting or precedence of macros. Sometime final user should not see or have access the internal macros which cause confusion, wrongly using them and overwriting other vars. It is always good to specify and restrict the scope of variable.
--Mohammad On Friday, August 30, 2019 at 1:25:24 PM UTC+4:30, @TiddlyTweeter wrote: > > Mohammad > > I agree in the sense that the current approach is largely "flat", not > "hierarchical". Its a "bucket" of all sorts. > > BUT, to be honest, I never had problems with it. > > *How much of an issue is this from the point-of-view of an end user?* > > Just thoughts > Josiah > > Mohammad wrote: >> >> Proposal >> >> Like other programming language we can have sub macro or private members. >> For example TW core can prevent access to all macros in a tiddler tagged >> with $:/tags/Macro if their name meet some certian criteria for example: >> __NANE__ or __::NAME >> >> -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/6e9d0573-6d2b-43be-85a6-0b074a9de441%40googlegroups.com.
