You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
Not a real issue, but... a suggestion for documentation precision.. or language extension
As a former C++ developer I tried a C++ implementation from scratch, just with doc an examples. Excellent practice !!!
In the doc, when you introduce Value and ID, you do not specify that they are INTs. So in my implem, .-@"This dot ID is a string and dot has value "-#2-$@$#-& is valid
More: you can also define '+' operator, in C++, both with ints ans strings.
More: one could use floats in values as well ? .-#2.3 ?
Another syntax suggestion: reading @ or # as "adressing modes", @$ or $# should be valid sequences, much easier to parse and insure consistency since @{+} for example switches from "Value mode adressing" to "ID mode adressing".
Great language !
The text was updated successfully, but these errors were encountered:
Yeah I think the id vs address thing can sometimes be confusing. And I should definitely clarify in the documentation that the dots store floats. I'm a bit busy right now, so I'll keep this issue open to remind myself to update the docs.
Hi,
Not a real issue, but... a suggestion for documentation precision.. or language extension
As a former C++ developer I tried a C++ implementation from scratch, just with doc an examples. Excellent practice !!!
In the doc, when you introduce Value and ID, you do not specify that they are INTs. So in my implem, .-@"This dot ID is a string and dot has value "-#2-$@$#-& is valid
More: you can also define '+' operator, in C++, both with ints ans strings.
More: one could use floats in values as well ? .-#2.3 ?
Another syntax suggestion: reading @ or # as "adressing modes", @$ or $# should be valid sequences, much easier to parse and insure consistency since @{+} for example switches from "Value mode adressing" to "ID mode adressing".
Great language !
The text was updated successfully, but these errors were encountered: