Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 360840 - Bad error on timeStamp definition
Summary: Bad error on timeStamp definition
Status: CLOSED WONTFIX
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: EDT (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-13 10:50 EDT by broy2 CLA
Modified: 2017-02-23 14:15 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-13 10:50:59 EDT 
myTimeStamp timeStamp;	

Gives error:
IWN.VAL.3433.e 6/17 The type timeStamp is not instantiable. The reference to this type must be defined as nullable.

But when I add the ? and SysLib.writeStdout(myTimeStamp), I get:
A null value was used.
eglx.lang.NullValueException A null value was used

It's messing up a lot of my testcases.
Comment 1 Paul Harmon CLA 2011-10-13 11:44:52 EDT 
According to the new language document (on the EDT wiki), Timestamp without a pattern is a reference type in EDT (much like how Decimal is a reference type if no length is specified). Because of this, there is no default value for Timestamp...so it is not intstantiable.


You will either need to code a pattern on the definition or make the field nullable.
Comment 2 Paul Harmon CLA 2011-10-13 11:46:40 EDT 
You will probably want to change your definitions to Timestamp("yyyyMMddHHmmss"), as this was the previous default in EDT before I implmented the language change.
Comment 3 broy2 CLA 2011-10-13 15:09:02 EDT 
Well, OK.