search

eclipse-ocl / org.eclipse.ocl

Eclipse Public License 2.0
0 stars 0 forks source link

[library] null is not the singleton instance of OclVoid #442

Closed eclipse-ocl-bot closed 3 hours ago

eclipse-ocl-bot commented 3 hours ago

| --- | --- | | Bugzilla Link | 290315 | | Status | CLOSED FIXED | | Importance | P3 normal | | Reported | Sep 23, 2009 15:39 EDT | | Modified | May 29, 2012 13:20 EDT | | Version | 1.3.0 | | Blocks | 156363 | | Reporter | Ed Willink |

Description

The current implementation of OCL's null uses Java's null. This may be pragmatic but requires considerable analysis to provide it's validity and considerable coding care and review to distinguish inadvertant Java nulls particularly those meaning invalid.

I think we should introduce a true null object that is indeed the sole instance of OclTYpe, with an OclStandardLibrary.getNull() that returns it.

eclipse-ocl-bot commented 3 hours ago

By Ed Willink on Feb 01, 2011 01:52

The new evaluator continues to use Java-null, and Java-exception as lazy alternatives to OCL-invalid. OCL-invalid returns are preferred since they may carry subsidiary information such as reasons and exceptions.

OCL-null is always explicit.

eclipse-ocl-bot commented 3 hours ago

By Ed Willink on May 27, 2011 06:40

Resolved for Indigo is 3.1.0 not 3.2.0.

eclipse-ocl-bot commented 3 hours ago

By Ed Willink on May 29, 2012 13:20

Closing all bugs resolved in Indigo.