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
u already know that there is extremely large population which hates python due to its significant whitespace issue, including myself. It just backtracking to 1970s.
"Boo programming language" has two modes- one python inspired syntax (white space significant) and another whitespace agnostic mode
why can't it be offered by you
moon -nowhite file1.moon (using commandline switch OR a switch in API)
can process "begin.. end" blocks to convert them to tabs internally
or still better,
moon file1.moonx (moonx file extension will show that it has to be processed in whitespace agnostic mode) (I WILL PREFER THIS FILE EXTENSION BASED APPROACH)
or, moonx file1.moonx
in api also, if you have parse_code("moon_filename") , then you can extend it as parse_codex("moonx_filename") to deal with whitespace agnostic mode.
but why are you hampering the adoption of your language , just because you want to force people to use the whitespace issue , which is an editor/IDE issue to make it as a language source syntax issue. Still wherever or internet, it is discussed there are always two big camps (python guys and non-python(ruby,lua,groovy,C++,vb.net,C# etc) guys fighting this whitespace issue.
THIS significant whitespace is just plain braindead, we (me , my friends, my colleagues) just can not stand it, it just stinks.
The text was updated successfully, but these errors were encountered:
keeping this whitespace issue apart, your language idea compiling to lua code and offering better high level abstractions over lua is highly praiseworthy.
I don't have the resources to support two versions of the language. It is still very early in development and there will be a lot of changes to come. Trying to have two syntaxes during this time would be very painful.
Additionally, you don't have any argument as to why white space sensitivity is an issue, other than it "stinks".
I'm sorry that I can't please everyone, but this is one change I don't plan on making.
Feel free to fork the project. The compiler and the parser are not tightly coupled, it is very easy to replace one while still keeping the other.
u already know that there is extremely large population which hates python due to its significant whitespace issue, including myself. It just backtracking to 1970s.
"Boo programming language" has two modes- one python inspired syntax (white space significant) and another whitespace agnostic mode
why can't it be offered by you
moon -nowhite file1.moon (using commandline switch OR a switch in API)
can process "begin.. end" blocks to convert them to tabs internally
or still better,
moon file1.moonx (moonx file extension will show that it has to be processed in whitespace agnostic mode) (I WILL PREFER THIS FILE EXTENSION BASED APPROACH)
or, moonx file1.moonx
in api also, if you have parse_code("moon_filename") , then you can extend it as parse_codex("moonx_filename") to deal with whitespace agnostic mode.
but why are you hampering the adoption of your language , just because you want to force people to use the whitespace issue , which is an editor/IDE issue to make it as a language source syntax issue. Still wherever or internet, it is discussed there are always two big camps (python guys and non-python(ruby,lua,groovy,C++,vb.net,C# etc) guys fighting this whitespace issue.
THIS significant whitespace is just plain braindead, we (me , my friends, my colleagues) just can not stand it, it just stinks.
The text was updated successfully, but these errors were encountered: