-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Var and ID possible values, Syntax suggestion #95
Comments
Thanks for the feedback! 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. Cheers! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: