Nope, likely just some overly zealous cleanup work. Rick
On Tue, Aug 26, 2008 at 5:37 PM, Mark Miesfeld <[EMAIL PROTECTED]> wrote: > Rick, > > You cleaned up the code in the CONDITION builtin secion, but also > changed the behavior when there is no condition object. > > In 3.2.0, when there is no condition object, the C, D, I, and S > options all returned the empty string. Only the O and A options > returned .nil when there was not a condition object. > > In 4.0.0, again when there is no condition object, the C, D, and S > options return .nil. The I option still returns the empty string. > But, from a comment in the code it looks like that might be by > accident. <grin> > > return OREF_NULLSTRING; /* should never happen > */ > > Did you intend that change? > > -- > Mark Miesfeld > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Oorexx-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
