several issues in DvTime

Bug #612590 reported by Sergio Miranda Freire on 2010-08-02
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Diego Manhães Pinheiro

Bug Description

Argument magnitudeStatus is missing in the initializer and in the call to the superclass initializer.
magnitude is an derived attribute, so it does not need to appear as an argument in the initializer.

DvDate inherits from DvAbsoluteQuantity and ISO8601Time (support package). So it is necessary to implement all methods of both classes, namely:
      add, subtract, diff, compare, isStrictlyComparableTo (DvAbsoluteQuantity)
     asString, hour, minute, second, hourUnknown, minuteUnknown, fractionalSecond, hasFractionalSecond, timezone, secondUnknown isPartial, isExtended, isValidISO8601Time, isDecimalSignComma (ISO8601Time) and enforce the invariants:
Hour_valid: valid_hour(hour, minute, second)
Minute_valid: not minute_unknown implies valid_minute(minute)
Second_valid: not second_unknown implies valid_second(second)
Fractional_second_valid: has_fractional_second implies (not second_unknown
and valid_fractional_second(fractional_second))
Partial_validity: minute_unknown implies second_unknown

Related branches

Changed in oship:
importance: Undecided → High
milestone: none → 1.5
Changed in oship:
assignee: nobody → Diego Manhães Pinheiro (dmpinheiro)
affects: oship → oshippy
Changed in oshippy:
milestone: 1.5 → none
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers