Project

General

Profile

Feature #1729

implement better default naming rules

Added by Eric Faulhaber over 13 years ago. Updated about 4 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
FWD - Converted Code Improvements - Deduplication
Start date:
Due date:
% Done:

0%

Estimated time:
32.00 h
billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:

History

#1 Updated by Eric Faulhaber over 13 years ago

  • add hints support for naming overrides
  • resolve cross-namespace (vars, streams....) conflicts
  • minimize the use of disambiguating text in the names (like prefixing Frame to every frame name)

#2 Updated by Greg Shah over 13 years ago

  • Target version set to Code Improvements

#3 Updated by Greg Shah over 9 years ago

  • Target version changed from Code Improvements to Converted Code Improvements - Deduplication

#4 Updated by Greg Shah about 4 years ago

We have a customer which commonly has an OO 4GL class name (XYZ.cls) which is the same as a temp-table name (XYZ). This results in their classes having the name XYZProgram while the temp-table has XYZ. If we did not do this, then the references to the temp-table would need to be fully qualified in the converted XYZ program (and any other program in that package or which imports that package). They want us to consider alternatives.

<rant> Our default conversion is a slave to our evil Persistence Overlords. </rant>

Also available in: Atom PDF