I posted this to -qa and -internal, since I was suggesting this
for the internal development of perl. Not for the user visible
pieces.
If we will be going through an intermediate language, then that
language should/could/will/might support such specifications.
Then under appropriate prodding will include or exclude them
based on the build requested.
<chaim>
>>>>> "MGS" == Michael G Schwern <[EMAIL PROTECTED]> writes:
MGS> On Sun, Aug 13, 2000 at 07:16:41PM -0400, Chaim Frenkel wrote:
>> What do you think of creating a mechanism for attaching pre-, post-,
>> invariant conditions to the internals?
MGS> I'd like to point out that two modules already do this.
MGS> Class::Contract which was just unleashed by Damian Conway, and
MGS> invariant.pm which Abigail recently posted up to Fun With Perl.
MGS> Class::Contract is by far the more complete.
MGS> I wouldn't mind an optional OO contract system in the core of Perl,
MGS> but this may be a case of "why do it in core when a module will work?"
MGS> Since OO contracts are typically turned off in production code any
MGS> performance gains from adding it to the core wouldn't matter much.
MGS> What we might want to do is ask Damian and Abigail (who have been
MGS> CC'd) if they have any feature requests which would allow them to
MGS> make their modules better/faster/more complete. We'd also want to
MGS> consider distributing Class::Contract with perl6 (or perl5 even).
--
Chaim Frenkel Nonlinear Knowledge, Inc.
[EMAIL PROTECTED] +1-718-236-0183
