c2c-oerpscenario team mailing list archive

[Numérigraphe <673087@xxxxxxxxxxxxxxxxxx>]

This is of course a wishlist item, not something to be fixed right now.

** Description changed:

  There are lots of small spelling mistakes throughout the code : datas=data, childs=children, logistic=logistics etc.
  I think these deserve to be fixed one day.
  
  The point of correct English in the code is:
  - well-written code is a documentation in itself
+ - you can't search for misspelled words in IDEs
  - bad English is a clue to find code that was never reviewed nor refactored
  - respect for your fellow developers worldwide
  
  It's not risky because:
  - renaming variables and functions is easily and quickly done (ecplise even has a wizard for it)
  - bzr lets you review what you merge
  - yml tests will catch the problems
  Lionel

** Description changed:

  There are lots of small spelling mistakes throughout the code : datas=data, childs=children, logistic=logistics etc.
  I think these deserve to be fixed one day.
  
  The point of correct English in the code is:
  - well-written code is a documentation in itself
  - you can't search for misspelled words in IDEs
  - bad English is a clue to find code that was never reviewed nor refactored
  - respect for your fellow developers worldwide
  
  It's not risky because:
  - renaming variables and functions is easily and quickly done (ecplise even has a wizard for it)
  - bzr lets you review what you merge
  - yml tests will catch the problems
  Lionel
+ 
+ Related bugs : Bug #326160, Bug #327259

-- 
Spelling errors in the code
https://bugs.launchpad.net/bugs/673087
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.

Status in OpenObject Addons Modules: New

Bug description:
There are lots of small spelling mistakes throughout the code : datas=data, childs=children, logistic=logistics etc.
I think these deserve to be fixed one day.

The point of correct English in the code is:
- well-written code is a documentation in itself
- you can't search for misspelled words in IDEs
- bad English is a clue to find code that was never reviewed nor refactored
- respect for your fellow developers worldwide

It's not risky because:
- renaming variables and functions is easily and quickly done (ecplise even has a wizard for it)
- bzr lets you review what you merge
- yml tests will catch the problems
Lionel

Related bugs : Bug #326160, Bug #327259