search

rlove / ut3

This is repository contains a proposal for how to build utPlSQL version 3.
Apache License 2.0
1 stars 0 forks source link

mixed camelCase and snake_case #1

Open jgebal opened 8 years ago

jgebal commented 8 years ago

One of the things that I've found a bit dirty with utPlsql was mixing standards of coding and API. Do you think it would be possible to start with clean slate and keep consistency on one approach? the camelCase though tempting isn't really good for PLSQL mainly due to IDE's and code formatters that can easily make code unreadable by change from areEqual to AREEQUAL or areequal depending on IDE and settings. are_equal seems more Oracle way.

rlove commented 8 years ago

Yes I think we can get consistent. Right now I don't like formatting in my code base and mentioned it in the readme.md file. I can see your point about camel case. On Feb 24, 2016 4:50 PM, "Jacek Gębal" notifications@github.com wrote:

One of the things that I've found a bit dirty with utPlsql was mixing standards of coding and API. Do you think it would be possible to start with clean slate and keep consistency on one approach? the camelCase though tempting isnt really goof dor PLSQL mainly due to IDE's and code formatters that can easily make code unreadable by change from areEqual to AREEQUAL or areequal depending on IDE and settings. are_equal seems more Oracle way.

— Reply to this email directly or view it on GitHub https://github.com/rlove/ut3/issues/1.