UML 2.5 FTF Avatar
  1. OMG Issue

UML25 — Default value for LiteralReal

Open Closed All
  • Key: UML25-265
  • Legacy Issue Number: 17818
  • Status: closed  
  • Source: Change Vision ( Michael Chonoles)
  • Summary:

    Why does LiteralReal have no default value?

  • Reported: UML 2.4.1 — Wed, 26 Sep 2012 04:00 GMT
  • Disposition: Resolved — UML 2.5
  • Disposition Summary:

    The only reason that certain LiteralSpecifications still have default values in UML 2.5 is for backward compatibility
    with the UML 2.4.1. When LiteralReal was added in UML 2.5, it was decided not to compound the problem by giving
    LiteralReal a default value. (In addition, no UML tooling yet supported LiteralReal, since it was new, which made
    including a default real value in the UML metamodel difficult.)
    (See also the resolution to Issue 17817.)
    Disposition: Closed - No Change
  • Updated: Fri, 6 Mar 2015 20:59 GMT