Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

Precondition (@Requires) should be checked before the method, closure is invoked

#25

The converse is true for the post conditions (@Ensures).
The check should be after the the method, closure invocation.

class G {

String g

}

class H {

@Requires({ g != null })
static void h(G g) {
    g.g
}

}

if you call H.h(null) it will fail with a null pointer exception instead of AssertionViolation (more specifically PreconditionViolation)

Reported by Thomas Han · May 18th, 2011 @ 09:47 AM

State: resolved
Milestone: 1.2.4

Activity

  1. me (at andresteingress)
    me (at andresteingress)
    • Milestone set to 1.2.3
    • Assigned user set to me (at andresteingress)
    • Milestone order changed from 3 to 0

    May 18th, 2011 @ 11:10 AM

  2. me (at andresteingress)
    me (at andresteingress)
    • Milestone changed from 1.2.3 to 1.2.4
    • Milestone order changed from 8 to 0

    May 18th, 2011 @ 11:16 AM

  3. me (at andresteingress)
  4. me (at andresteingress)
    me (at andresteingress)
    • State changed from new to resolved

    May 30th, 2011 @ 12:40 PM

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.