This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 260080 - Use of toOSString vs. use of toPortableString
Summary: Use of toOSString vs. use of toPortableString
Status: CLOSED WONTFIX
Alias: None
Product: Tigerstripe (Archived)
Classification: Technology
Component: Core (show other bugs)
Version: 0.4.4   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: 0.5M0   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-06 13:35 EST by Eric Dillon CLA
Modified: 2012-03-05 13:57 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Dillon CLA 2009-01-06 13:35:19 EST 
A search on toOSString on TS code show 80+ occurrences.
This is potentially leading to problems when running on PC vs Mac.
toPortableString should be used, in conjunction with the IFile.Separator to ensure consistency.
Comment 1 Navid Mehregani CLA 2012-03-05 13:57:11 EST 
I'm not sure if I agree with this change.  According to the APIs, toPortableString doesn't have a specified format.  Yet there are instances in TS code where we call toOSString and further modify the returned string.  We can't do that with toPortableString, since the format is unspecified.

If there are specific instances where usage of this API causes issues between PC/Mac, please reopen this defect and provide more details so we can further investigate.