[progress Communities] [progress Openedge Abl] Forum Post: Pitfalls For Camelcasing File Names?

  • Thread starter Thread starter Nick Vancauwenberghe
  • Start date Start date
Status
Not open for further replies.
N

Nick Vancauwenberghe

Guest
Our current rule in place: all file names lower-cased. This rule meets Progress portability guideline: https://documentation.progress.com/output/ua/OpenEdge_latest/index.html#page/wp-codeport/case-sensitivity.html However more and more developers are complaining about the readability impact: thisproceduredoesthis.p vs. ThisProcedureDoesThis.p *If* we would change our rule: file names should UpperCamelCased. What are the possible pitfalls? In other words, what do we need to pro-actively check/test to avoid issues at runtime. Taking into account that most server code runs on a case-sensitive linux os. Can this be summarized in a step by step checklist? The source file name is the truth. Make sure old lower-cased r-code is deleted. All code references should use the exact same cased name ... How can these checks/tests be automated? To catch all mistakes overlooked by a developer before deploy.

Continue reading...
 
Status
Not open for further replies.
Back
Top