A pitty , I think python has the same limitations with whitespace. Its kinda weird because python forces indentation as part of the syntax ( a reason why some people hate python) and yet it finds it perfectly fine to do a 3-4 which to me is pretty much a very obvious readability problem (at least something my math teacher would have complained about ;) ).
But none the less, I am ok with camel case , and I am certainly ok with how pharo forces naming conventions. I find documentation a lot bigger deal for a coder than how he names methods and classes. Also it should not be so hard to implement a parser (PettitParser ? ) for adding those features in , without changing pharo or smalltalk syntax , as a third party library. Afterall thats the purpose of OOP , to extend and not to modify code :) The one thing I was thinking for implementing for my project Ephestos, was a more english language version of smalltalk , where a name of a class can have even whitepaces inside it. I have to confess its a rather low priority idea for now, cause I am already over my head with opengl and nativeboost but it would be a fun area to explore. I was thinking replacing lisp parentheses in some way with graphical elements that dicate where the name starts and ends and where the parameters also start and end. A bit like Scratch but much more transparent without kicking out standard smalltalk syntax. For example ((3d cube morph ) (draw on screen ( x : 500 y: 400 ))) . where parentheses represent graphical elements (user wont type parentheses but rather use key shortcuts, maybe tabs ) in the text editor which could be made transparent so the code reads (and hovering the mouse on top of class and methods names could make visible the graphical elements again) 3d cube morph draw on screen x :500 y: 400 . With autocompletion to cut down typing and even autofill in the class name just by using the method name ( if same methods exist in other classes a drop down menu autocompletition style will allow him to choose the right class). The above of course will still be commited as smalltalk code 3dCubeMorph drawOnScreen x: 500 y:400 so it will be more like an illusion for the coder, for pharo will be regular smalltalk code. Of course that has the advantage of existing smalltalk code being displayed with this syntax , again with zero changes to source code commited. Its an idea I would like to try at some point, no promises when :D -- View this message in context: http://forum.world.st/Pharo-dev-Lowecase-class-names-tp4690963p4691944.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
