Skip to content
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

Auto completion in lowercase #9

Closed
Guibuu opened this issue Jan 27, 2018 · 3 comments
Closed

Auto completion in lowercase #9

Guibuu opened this issue Jan 27, 2018 · 3 comments

Comments

@Guibuu
Copy link

Guibuu commented Jan 27, 2018

Hi, I have just discovered this project and it's a bless! I'm trying to learn some GDL and this syntax highligthing is very helpful. Great work. Seriously.

In the naming conventions section of the Graphisoft's GDL Center, in 'Capitalization', Graphisoft recommends writing commands in lowercase. I too prefer that, makes the code more friendly. I'm curious, why did you decide the auto completion to suggest commands in uppercase? Could you… ahem… change that to lowercase? I think I know the answer, but still I have to try ;)

Thank you very much!

@runxel
Copy link
Owner

runxel commented Feb 7, 2018

Guibuu, glad to hear that »GDL-sublime« is a help to you. Thanks a bunch!

So whats with the capitalization? That's the influence of the famous »GDL Cookbook« by David Nicholson-Cole. The author recommends writing GDL in uppercase – I know the official GS doc on that, tho. I sticked to him somehow.
That being said I'm not a big fan of all-caps as well – since most modern language recommendations say lower-caps. So I might as well change that at some point in the future. Depends on my free time ;)

For completeness' sake here the full comment on that topic by DNC (p. 22, GDL Cookbook # 3):

Typograpical note
In reading this you have already expressed a serious interest
in GDL – so let’s bring in a good discipline at the start.
Write all GDL commands in UPPER case, and all variables
(parameter names) and comments in lower case. The
machine is not case sensitive, but you are, and when reading
and debugging your scripts later, you will find it easier
if you follow this advice.
If you find yourself working on GDL as part of a team
you need to agree on a format, so this is a good rule to
follow. It is followed in the Cookbook.

@runxel
Copy link
Owner

runxel commented Feb 14, 2018

done in v2.1.0 :)

@runxel runxel closed this as completed Feb 14, 2018
@Guibuu
Copy link
Author

Guibuu commented Feb 14, 2018

That is AWESOME… I mean… awesome (in lower caps 😄 )

Also, thanks for explain me the original reason for the uppercases. It's a shame GDL Cookbook has become a little outdated, because there is little GDL documentation available.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants