Bug #6706
preserve existing camel-case usage in program names
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:
History
#1 Updated by Greg Shah almost 4 years ago
We have a customer that deliberately uses camel-case in their program names (especially in OO classes). The current FWD v4 doesn't preserve this, instead we lose knowledge during name conversion (MyCamelCase.cls becomes Mycamelcase.java) which is not a good result.
This task is meant to fix the issue.