Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 346692

Summary: Timestamp specs are lowercased in IRs
Product: z_Archived Reporter: Scott Greer <greer>
Component: EDTAssignee: Project Inbox <edt.mofmodel-inbox>
Status: CLOSED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: lasher, mheitz, pharmon
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Scott Greer CLA 2011-05-20 10:34:54 EDT
This line of EGL source

		const t timestamp("yyyyMMddHH") = "1987 03/18 10";


is represented in the IR with a fully lowercased timestamp specification which is obviously bad because the spec is case-sensitive.

				<expr ID="646" eClass="org.eclipse.edt.mof.egl.DeclarationExpression" >
					<fields ID="647" eClass="org.eclipse.edt.mof.egl.Field" name="t" type="egl:egl.lang.anytimestamp(yyyymmddhh)" isNullable="false" isStatic="false" isAbstract="false" hasSetValuesBlock="true" isImplicit="false" isSystemField="false" >
						<annotations ID="648" eClass="dynMof:org.eclipse.edt.mof.egl.Annotation:EGL_Location" len="i:1" off="i:3542" line="i:101" />
						<container IDREF="41"/>
						<initializerStatements ID="649" eClass="org.eclipse.edt.mof.egl.StatementBlock" >
							<statements ID="650" eClass="org.eclipse.edt.mof.egl.AssignmentStatement" >
								<annotations ID="651" eClass="dynMof:org.eclipse.edt.mof.egl.Annotation:EGL_Location" len="i:15" off="i:3570" line="i:101" />
								<expr ID="652" eClass="org.eclipse.edt.mof.egl.Assignment" >
									<LHS ID="653" eClass="org.eclipse.edt.mof.egl.MemberName" id="t" >
										<member IDREF="647"/>
									</LHS>
									<RHS ID="654" eClass="org.eclipse.edt.mof.egl.StringLiteral" value="1987 03/18 10" isHex="false" >
										<annotations ID="655" eClass="dynMof:org.eclipse.edt.mof.egl.Annotation:EGL_Location" len="i:15" off="i:3570" line="i:101" />
									</RHS>
								</expr>
							</statements>
						</initializerStatements>
					</fields>
				</expr>
Comment 1 Paul Harmon CLA 2011-06-24 12:56:35 EDT
I have fixed this by changing PatternTypeImpl.getPatter() to fix the case of the pattern.
Comment 2 Lisa Lasher CLA 2011-11-02 10:28:43 EDT
closing this defect for Scott