Opened 10 years ago
Last modified 7 years ago
#2954 new defect
package.order encoded UTF-8 with Byte Order Mark (BOM) is not properly handled
Reported by: | Adrian Pop | Owned by: | somebody |
---|---|---|---|
Priority: | high | Milestone: | Future |
Component: | Frontend | Version: | trunk |
Keywords: | Cc: |
Description (last modified by )
When we read package.order encoded in UTF-8 with BOM the first class name is mangled, if is MassFlowRate
then the name we read is: MassFlowRate
which will make the library un-loadable.
Change History (10)
comment:1 by , 10 years ago
Component: | Frontend → Parser |
---|---|
Description: | modified (diff) |
Owner: | changed from | to
Summary: | Short class definition as stored definition are not loaded → package.order encoded UTF-8 with Byte Order Mark (BOM) is not properly handled |
comment:2 by , 10 years ago
comment:3 by , 10 years ago
Component: | Parser → Frontend |
---|---|
Owner: | changed from | to
Yeah, it should be class loader, so FrontEnd I guess?
comment:4 by , 10 years ago
Milestone: | 1.9.2 → 1.9.3 |
---|
Milestone changed to 1.9.3 since 1.9.2 was released.
comment:9 by , 8 years ago
Milestone: | 1.11.0 → 1.12.0 |
---|
Milestone moved to 1.12.0 due to 1.11.0 already being released.
comment:10 by , 7 years ago
Milestone: | 1.12.0 → Future |
---|
The milestone of this ticket has been reassigned to "Future".
If you think the issue is still valid and relevant for you, please select milestone 1.13.0 for back-end, code generation and run-time issues, or 2.0.0 for front-end issues.
If you are aware that the problem is no longer present, please select the milestone corresponding to the version of OMC you used to check that, and set the status to "worksforme".
In both cases, a short informative comment would be welcome.
What does this have to do with the parser? The parser never reads package.order.