Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 359929 - Get cannot be resolved message on asNumber and asString
Summary: Get cannot be resolved message on asNumber and asString
Status: CLOSED WONTFIX
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: EDT (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P1 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-04 17:51 EDT by broy2 CLA
Modified: 2017-02-23 14:14 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 broy2 CLA 2011-10-04 17:51:19 EDT 
myNumber = myString.asNumber();                        	          
myString = myBigInt.asString(); 

IWN.VAL.6619.e 8/29 stringFunctions - myString.asNumber cannot be resolved. A
IWN.VAL.6619.e 9/24 stringFunctions - myBigInt.asString cannot be resolved.
Comment 1 Paul Harmon CLA 2011-10-11 11:23:07 EDT 
I am not sure where this came from? Is there a document that says that String should have a asNumber() function and BigInt should have an asString()?

I think the proper way to do this is:

myNumber = myString as Number;                                      
myString = myBigInt as String;
Comment 2 broy2 CLA 2011-10-11 11:50:28 EDT 
OK.  I didn't know how to read the EString code.
Comment 3 broy2 CLA 2011-10-11 12:46:57 EDT 
OK.