Amreus,
Often overlooked by people is the logical necessity of a prefix on some
parameters, once you understand this you may find yourself identifying when
the $ is likely to be used, rather than any need commit it to memory.
- In the case of the macrocall widget, what If I wanted to pass a
parameter called name, type or output ? they would be confused with the
widgets parameters,
- so $name, $type and $output ensure the widgets own parameters stay
out of the way.
- And you can also imagine when creating new tiddlers or fields the $ is
often used for the same reason, so as to not limit the names of parameters
that can be use.
- The new tiddler and set field and in fact all Action widgets must
use $ for the very same reason.
As an experienced programmer I have learned there are good reason for *a
lot of things people perceive as exceptions or complexity, to actually be
logical necessities. *
- You can see in this case the ability to have a prefixed parameter
"$name" is essential in some widgets.
- Unfortunately most documentation, for most systems, including
programming languages, do not explain these logical necessities.
- An example is the the mathematical order of precedence in
programming languages 4x(3x2+5), many languages document them *as if
they invented this*,
- however they were developed hundreds of years earlier in the field
of mathematics
- By not recognising this history, people are forced to remember
every detail "again", rather than rely on it mapping to historical
standards.
Regards
Tones
On Monday, 28 September 2020 03:06:12 UTC+10, amreus wrote:
>
>
> I see some widget's attributes start with a $ and some don't. Does the $
> have special meaning?
>
>
>
>
>
>
--
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/0419b859-a4b7-474a-ab7e-c295bc98f4c1o%40googlegroups.com.
