![]() Home |
![]() Map |
![]() OS++ Down Load |
![]() Doco_A |
![]() Youtube |
![]() Chat |
![]() News |
![]() Shop |
//#! Declaration: http://osplusplus.org/2022standard/
TLDR; This is in the top line of all OS++ user code. It is a standard declaration using the format (CODE.org/STANDARD/GRADE). You are using this declaration to notify future readers that the following code is written in OS++, with the 2022 syntax standard. To download the framework see the link below.
Download OS++ framework - P7zip Best compression >>> http://osplusplus.org/2022standard/The_Download.7z
Download OS++ framework - lrz >>> http://osplusplus.org/2022standard/The_Download.tar.lrz
Download OS++ framework - Winzip compression >>> http://osplusplus.org/2022standard/The_Download.zip
Download OS++ framework - Okay compression >>> http://osplusplus.org/2022standard/The_Download.tar.gz
Download OS++ framework - Worst compression >>> http://osplusplus.org/2022standard/The_Download.tar.Z
The Standards declarations are as follows:
The excuse declarations are as follows:
For more info on grades see http://osplusplus.org/2022standard/Professional
All this means is that the ultimate canon is in the code, not the documentation.
This means if an idea, coding standard or concept does not fit into the current standard. Then a new standard needs to be created. If the market does not like the new standard, then it’s a signal that the author (me) has taken a wrong turn. I should not be allowed to deprecate a feature and enforce my new thinking on the world.
This is a first release date. I intend to flesh out ideas in later years. As long as the ideas are accumulative and I can “shoe horn” them into the old standard, the name will remain constant. Backward compatibility is key.
The ideas is that once someone understands one library. eg cuboids. That knowledge should be transferable, as much as possible, to the rest ie cones and sphere.
Well as much as is possible in the openscad ide.
This is a noble attempt to write a language which is readable by people who did not write the original user code. Or more importantly make my current user code readable by me in a few years time. Nothing is more humbling than looking at user code and thinking “What mad man wrote this code?” Only to find out, once you check your version control system, it was you.
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|