HaloO,
Ovid wrote:
In other words, I think we could get proper constraint programming if a
subset can mutate its variable. Otherwise, all assignment would need
to be wrapped inside of an eval and the code would be more bug-prone.
I must admit that I hardly follow that statement. Why are
HaloO,
Daniel Ruoso wrote:
In fact, I doubt that there's a way to completely avoid any possible
side effects on this closures. as the very first line of the closure
shows:
$_.inside_of(...)
This is a plain method call, there's no way to tell if this method will
change anything inside the
HaloO,
David Green wrote:
I would expect all of those to work the same way in either case. That
is, anywhere the sub is used as an lvalue, it could pass the rvalue as a
special arg, not just when using =.
I agree. But I want to stress that the big thing is that a lvalue
sub---and to a
--- TSa [EMAIL PROTECTED] wrote:
I must admit that I hardly follow that statement. Why are
side-effects
essential to achieve constraint programming and why do you think that
the way to get at the constraint programming paradigm are the subset
type definitions?
Because I can't think of any
--- TSa [EMAIL PROTECTED] wrote:
Daniel Ruoso wrote:
In fact, I doubt that there's a way to completely avoid any
possible
side effects on this closures. as the very first line of the
closure
shows:
$_.inside_of(...)
This is a plain method call, there's no way to tell if
HaloO,
On Monday, 16. June 2008 10:11:49 Ovid wrote:
For example, should the pre/postfix '++' be
listed as having a side-effect?
I think so. But the scope where these side-effects take
place is important as well. In your second example below
the side-effect is restrained to the subs scope.
HaloO,
On Monday, 16. June 2008 10:03:13 Ovid wrote:
--- TSa [EMAIL PROTECTED] wrote:
... why do you think that
the way to get at the constraint programming paradigm are the subset
type definitions?
Because I can't think of any other way to do it :)
So I´ll try to come up with some
HaloO,
On Saturday, 14. June 2008 18:43:05 Daniel Ruoso wrote:
Moritz convinced me that there's actually no real reason to support
$nonlist.listmethod
I wouldn´t do that either. But I come to that conclusion from the
line of thought that it is generally a bad idea to block an Any
slot in a
