From: "Wood, Jeff" <jeffwood@...>
Date: 2004-11-18T02:16:07+09:00
Subject: Re: assert

------_=_NextPart_001_01C4CCC9.1E661BC4
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

It's a semantic thing, but you could also go with an #ensure name

But, I guess I have a question, why not just have a function that =
switches asserts to either raise an exception or cause an IRB session?  =
that way you could KNOW your code isn't going to break into IRB in it's =
production environment, unless you specifically ask it to...

Anyways, I'd be happy with either...

# One time call to switch on irb asserts.
irb_assert true
.
.
.
assert b =3D=3D 5


...

or maybe just irb_assert as the syntax for an assert that causes an IRB =
session ...=20

assert b =3D=3D 5 # throws exception
irb_assert b =3D=3D 5 # starts irb

...just throwing ideas.

j.

------_=_NextPart_001_01C4CCC9.1E661BC4--