econditions
work in the opposite direction, they don't quite gel with that particular
proposal.
Mike Lambert
on is not
really a problem since one can always add additional checks. However, if
the parent's preconditions apply to the child invariably, it would be
rather difficult to make your subclass accept a wider variety of input.
I'm not proposing a solution, but rather just a problem to keep in mind.
Mike Lambert
(.*) }
"a union" => "a "
"b" => "b"
Am I missing something here?
Mike Lambert
ple is perfectly fine?)
What about:
$a = 1,2,3
($a) = (1,2,3)
$a = (1,2,3)
($a) = 1,2,3
Do you still believe those should be identical? They have the same
problems mentioned above, and likely other issues as well.
Mike Lambert
example is somewhat contrived, but I still
believe it illustrates a problem which *will* arise in practice.
Mike Lambert
sible avenues now, to be discarded as we
approach the implementation phase and realize the scope of the project. :)
Thanks,
Mike Lambert
sender' on
it.
I'm not sure how to describe pointers in the forest to the surrounding
mountains, however. Rainbows with a pot of gold at the mountainous end?
Telescopes on the ground which can be moved and rotated?
Mike Lambert
ed upon internal profiling would be
cool. But that's the topic of a different thread. :)
Of course, this is all starting to impose on p6i territory. I don't like
to start cross-posting unnecessarily, so someone please do that if it's
appropriate.
Thanks,
Mike Lambert
to it? The latter would occur with the
Perl5 solution above, and I would argue that it should stay that way,
since it's not exactly the same type.
Mike Lambert
Luke Palmer wrote:
> Date: Wed, 15 May 2002 19:51:39 -0600 (MDT)
> From: Luke Palmer <[EMAIL PROTECTED]>
> To: [EM
causes people to write:
for(int i=0; ... ) { ... }
for(i=0; ... ) { ... }
Which of course breaks when you remove the first loop. I always found that
annoying...and that's what the following was used for, in those compilers:
#define for if(0) {} else for
Mike Lambert
;t break the holy scoping rules. And
given how little you're going to want to know what kind of false value as
returned, I don't think it's that bad. Someone might want to come up with
a better variable name, however.
Just trying to contribute something new to the discussion that hasn't been
mentioned a dozen times already... :)
Mike Lambert
the regex stuff
become orthogonal. Rather than creating a bunch of hardcoded types of (?>=
regex operators, instead define small functionalities which can be
combined in ways to emulate these tried and true constructs.
Brent, let me know if I'm still spouting gibberish on this email. :)
Mike Lambert
#x27;})\E}
(?eval and 'r'=>regex-interpolate to handle:
{e print "hello"} and {r $code = calculation($&);qr/$code/}
(Assuming you want to keep these seperate, and don't want to force 'e' to
become {r print "hello";qr//} where qr// represents an empty regex that
doesn't insert anything into the regex stream.
I think I'll stop here, as I think I've said more than enough.
Mike Lambert
based
on some unique object identifier (memory address) that's constant
throughout the life of the object. This means that in order for an object
to be able to have equality work in hashtables, from two objects
constructed at different points in time, they'd need to overload the
operator
14 matches
Mail list logo
