time.
--
Mark J. REED[EMAIL PROTECTED]
, which I would
further expect to do the same way I would set any other attribute at
any other time. Orthogonality has its good points, even in Perl;
you just shouldn't be afraid to veer off diagonally when it makes sense.
I don't think close(var) makes sense.
--
Mark J. REED[EMAIL PROTECTED]
-level inheritance (since
it's the only way to go in prototype-based OO), but I hope we
wouldn't sacrifice class-level inheritance for it.
We could have both, right? We could let classes be first-class
objects, eh?
--
John Porter
--
Mark J. REED[EMAIL PROTECTED]
On Wed, Jun 27, 2001 at 03:07:36PM -0400, John Porter wrote:
Mark J. Reed wrote:
... be sure that Perl stays Perl.
Eh, puke.
I'm sorry? If you don't like Perl as it is, why do you care what happens
to it in the future? But the RFC on Perl remaining Perl has been accepted,
so let's move
be a settable property of properties?
--
Mark J. REED[EMAIL PROTECTED]
--
I have made this letter longer than usual because I lack the time to
make it shorter.
-- Blaise Pascal
bears and even
teddy bears get drunk
--
Mark J. REED[EMAIL PROTECTED]
and the conflation of names in typeglobs,
though I find it odd that nobody ever made a special case to disallow
them in Perl5. Of course, most global magic variables are going away,
anyway, but I think $n for regexes is remaining, right?
--
Mark J. REED[EMAIL PROTECTED]
the
current version:
while (my ($key, $val) = each %my_hash)
{ ... }
--
Mark J. REED[EMAIL PROTECTED]
Well, other than the fact that the while(each) doesn't do aliasing.
Since that would be the whole point, ignore that last message.
On Fri, Jul 20, 2001 at 01:21:57PM -0400, Mark J. Reed wrote:
On Fri, Jul 20, 2001 at 11:17:13AM -0600, Sterin, Ilya wrote:
But this will be flattened, so I
interpolation at the moment) $a_$b should result in an error about
$a_ being undeclared - if you use strict. You do use strict, right? :)
Mark J. REED[EMAIL PROTECTED]
Well, my head is definitely spinning. :) Thanks, Damian.
One oversight (on one of our parts - you either didn't put it in or I
didn't see it. :)): it looks like the example uses the new ; operator
(between the mandatory and option arguments in the function declaration?),
but it's not mentioned
());
--
Mark J. REED[EMAIL PROTECTED]
variable is magically inserted into the
loop block's lexical scope, even though it's declared outside of
the latter's curlies)? If so, I must have missed a mind-change in
that thread; if not, then putting the 'my' inside the parens is a
tad misleading . . .
--
Mark J. REED[EMAIL PROTECTED]
of step 5
is not an lvalue.
Then again, it's probably using some syntax that I haven't internalized
yet.
--
Mark J. REED[EMAIL PROTECTED]
; # syntax error
Doesn't that violate your stated rule thatthe default topic within a
method be the invocant? Shouldn't .m2 be equivalent to $_.m2?
--
Mark J. REED[EMAIL PROTECTED]
of
that decision having been made. I guess we won't find out for sure
until either Apoc6 or Apoc12?
--
Mark J. REED[EMAIL PROTECTED]
m1 was called
m2() # call subroutine m2 with no arguments, implied or otherwise
--
Mark J. REED[EMAIL PROTECTED]
On Wed, Apr 10, 2002 at 03:03:45PM -0400, Mark J. Reed wrote:
..class.m2: # call static m2 within m1's class, regardless of how m1 was called
Typo. That should be just .class.m2, only one leading '.'.
--
Mark J. REED[EMAIL PROTECTED]
On Wed, Apr 10, 2002 at 12:12:56PM -0700, David Whipp wrote:
Mark J. Reed wrote
On Wed, Apr 10, 2002 at 03:03:45PM -0400, Mark J. Reed wrote:
..class.m2: # call static m2 within m1's class, regardless
of how m1 was called
Typo. That should be just .class.m2, only one leading
'.' in front of
the m2(). In other words, unary . is the same as binary . with $_ as
the LHS, so .m2() would be the same as $_.m2(). Which would have the
semantics in my comment above, assuming that the class becomes the topic
in static methods.
--
Mark J. REED[EMAIL PROTECTED]
On Wed, May 01, 2002 at 12:11:58PM -0700, Brent Dax wrote:
It's far too late to make it into 5.8, but it looks like it'll be in
5.10 when that comes out (in a year or two).
.. . . by which time 6.0 will have already been released, right?
Right?
--
Mark J. REED[EMAIL PROTECTED]
On Sun, May 12, 2002 at 12:30:20AM +0200, Pixel wrote:
FYI Ruby has:
a.type = b.type or a.type == b.type
where the various operators (, , ==, != ...) are overloaded
according to the subtyping relation.
as for me,
- i find the == very readable,
- but i'm not sure = is very
On Tue, Jul 02, 2002 at 09:56:46AM +0100, [EMAIL PROTECTED] wrote:
Sean O'Rourke [...] presented a larger [grammar] that appears to
capture much more of the syntax found in Apocalypses and Exegeses
1 - 4 (5 just scares me).
On that subject, am I correct that there is no Exegesis 5
On Tue, Jul 16, 2002 at 05:42:18PM -0400, Michael G Schwern wrote:
I don't know how Java and Python handle Unicode.
Java has always been 100% Unicode from the ground up; it's in the spec.
The fundamental char type is a 16-bit value, you can use any letterlike
characters in identifiers, there's
On Wed, Jul 17, 2002 at 04:17:15PM +0100, Nicholas Clark wrote:
My understanding was that Unicode has now escaped the base plane (or whatever
it's called) and now has started using code points 65536. How does Java
cope with this?
This is getting a little off-topic, I think. But here's a brief
On Wed, Jul 17, 2002 at 12:13:47PM -0400, Dan Sugalski wrote:
I thought Java used UTF-16. It's a variable-width encoding, so it
should be fine. (Though I bet a lot of folks will be rather surprised
when it happens...)
UTF-16 isn't technically a variable-width encoding, since
surrogate codes
On Wed, Jul 17, 2002 at 12:13:47PM -0400, Dan Sugalski wrote:
I thought Java used UTF-16. It's a variable-width encoding, so it
should be fine. (Though I bet a lot of folks will be rather surprised
when it happens...)
Update:
Since Unicode 3.1 (3.2 is the current version), there have in
On Fri, Aug 02, 2002 at 08:30:05AM +1000, Damian Conway wrote:
@arr[@arr.length] = $var;
or maybe just :
@arr[.length] = $var;
(if an array were to be made the topic inside its own accessor brackets).
I know this idea was just thrown in there, but I find that I really
On Sat, Aug 10, 2002 at 02:23:07AM +0800, Christian Renz wrote:
Actually, I once found myself wondering why while doesn't set $_ all
the time anyway... It would be nice to do things like
Because the logic of the while construct doesn't require any
connection between the condition and the topic
On Fri, Aug 09, 2002 at 05:23:58PM -0700, Steve Fink wrote:
Wow. Since you went to the trouble of writing all this up, it really
ought to go in a FAQ somewhere.
It probably already is in a FAQ somewhere; I just don't know where. :)
On Thu, Aug 08, 2002 at 12:05:00AM -0400, Mark J. Reed wrote
The specific definitions of these terms vary from language to
language. In Java, for instance, a method is said to be
overloaded and/or overridden.
An overloaded method is actually two or more methods with the
same name but differing numbers/types of parameters (which Java
calls the signature
On Fri, Sep 06, 2002 at 02:34:52PM +0100, Nicholas Clark wrote:
On Wed, Sep 04, 2002 at 10:46:24PM -0400, Ken Fox wrote:
What is really needed is something that converts the date syntax
to normal Perl code:
rule iso_date { (Perl.term) -
(Perl.term) -
On Mon, Sep 09, 2002 at 05:02:18PM -0400, Aaron Sherman wrote:
On Mon, 2002-09-09 at 06:05, David Helgason wrote:
Yeay! Golf...
If we are allowed to use all of perl6 in this particular (golf-)course,
I suggest:
Clearly I've missed a reference at some point. Presumably golf is used
On 2002-10-08 at 17:15:06, Larry Wall wrote:
Seriously, () is just a special token. We could easily have used a
special token like NULLLIST instead. What does INTERCAL use?
Well, INTERCAL doesn't have lists per se, but it does have arrays, whose
size is set by assignment: the lvalue is the
On 2002-10-14 at 19:58:50, Piers Cawley wrote:
I would expect Class to inherit from Object (along with everything
else). It might be worth looking at a Smalltalk image or two at this
point...
You might want to look at _Putting_Metaclasses_To_Work_ by Danforth and
Forman - or at Ruby, which
Actually, 1/0 is not NaN; it's +Infinity. You only get NaN out of
dividing by 0 if the numerator is either infinite or also 0.
The reason most implementations throw an error on division by 0
is that they either don't have a representation for infinity
(not a problem in IEEE floating point) or
On 2002-10-14 at 19:48:23, Mark J. Reed wrote:
Actually, 1/0 is not NaN; it's +Infinity. You only get NaN out of
dividing by 0 if the numerator is either infinite or also 0.
The reason most implementations throw an error on division by 0
is that they either don't have a representation
On 2002-10-14 at 20:15:33, Michael G Schwern wrote:
There are several verbal proofs why 1/0 is not +Infinity here:
http://mathforum.org/dr.math/faq/faq.divideby0.html
Yeah, that would be why I sent my followup. I did not mean to
imply that 1/0 is positive infinity in real world math.
On 2002-10-14 at 20:49:52, Michael G Schwern wrote:
It is also, as an example, the behavior required by the ECMAScript
specification.
Heh. Because Javascript does it is supposed to be an argument for? ;)
Heh, indeed. :) But seriously, you could do worse. JavaScript receives
a lot of
On 2002-10-17 at 22:52:49, Smylers wrote:
Larry Wall wrote:
$a .| $b# bitwise or
$a .! $b# bitwise xor
On glancing down your list I initially misread the bar as an exclamation
mark. I realize that this is a sample size of one, but certainly in
this terminal
On 2002-10-26 at 18:10:39, Michael Lazzaro wrote:
Larry wrote:
If one were going to generalize that, one would be tempted to go the Ada
route of specifying the radix explicitly:
Ada and others . . . ksh uses the # for this (in place of your colon below),
and I seem to recall that syntax
On 2002-10-28 at 16:39:10, brian wheeler wrote:
[The below is actually from Larry, not Michael]
explicit radix specifications for integers:
0123- decimal
2:0110- binary [also b:0110?]
8:123 - octal [also o:123?]
16:123
On 2002-10-28 at 16:54:26, Dan Sugalski wrote:
The post that started this thread was a complaint about
leading 0 meaning octal - which is counterintuitive to everyone the
first time they come across it in C or Perl or Java or wherever.
That's not entirely true. Granted the set of the people
What about specifying endiannes also, or would that be too low-level
to even consider? Currently I don't have any examples for where it
might even be used...
Literals are the wrong place to put that; they represent values, not
storage. Endianness should generally not be visible at the
On 2002-10-30 at 12:23:53, David Wheeler wrote:
This tells me that Mail.app, for some reason, didn't know that it was
supposed to use UTF-8 when showing Larry's mail. When I pasted his mail
into a UTF-8 document in Emacs, it looked fine.
Given that it's probably UTF-8 that Perl 6 source
On 2002-10-30 at 12:47:17, Larry Wall wrote:
(Anybody know of a version of pine that does UTF-8?)
Yes - it's called mutt. ☺
Seriously, I do highly recommend switching from pine to mutt. It's not
a completely painless transition, since mutt is more ELMlike than PINElike,
but I know many who have
On 2002-10-31 at 12:45:23, David Wheeler wrote:
Plus, it turns out not to be at all hard to type on Mac OS X. ;-)
Well, the angle quotes happen to fall within Latin-1, and so they're
easier to get to. On Windows you can either set up special key mappings or
just type ALT+171 for « and ALT+187
On 2002-11-04 at 12:26:56, Austin Hastings wrote:
1- ? and ? are really useful in my context.
Okay. Now can you get your mailer to send them properly? :)
On 2002-11-06 at 11:43:20, Jonathan Scott Duff wrote:
Will there be some shorter-hand way to say these?
@a = @grades[grep $_ = 90, @grades];
@b = @grades[grep 80 = $_ 90, @grades];
@c = @grades[grep 70 = $_ 80, @grades];
I think what you mean here is just
@a =
[Recipients list trimmed back to just the list - it was getting ridiculous.
So everyone will get only get one copy and it may take a tad longer to
get there . . .]
On 2002-11-07 at 17:07:46, Dan Sugalski wrote:
Attributes are class-specific for a variable (okay, class instance
specific, if
On 2002-11-07 at 15:28:14, Luke Palmer wrote:
From: Mark J. Reed [EMAIL PROTECTED]
Will something like that not be possible in Perl6?
I'm afraid that statement is false for all values of something :)
Good point. Erratum: for possible
On 2002-11-14 at 16:47:15, Michael G Schwern wrote:
string concatenation operator - please stop
http://archive.develooper.com/perl6-language;perl.org/msg06710.html
BTW, the first link there - to the bikeshed story - is broken.
This is the correct link:
On 2002-11-19 at 16:44:49, Me wrote:
Elements of this shared vocabulary might be
called 'locals' or 'yours'.
I like the 'yours' idea from the point of view of the callee:
my $inherited = your $_;
However, I also like the idea of having to mark shareable lexicals
explicitly in the
On 2002-12-06 at 17:59:33, Larry Wall wrote:
Now all we have to do is
convince everyone that the year 1 B.C. is the same as year 0 A.D.,
and 2 B.C. is the same as -1 A.D., and so on.
Well, since that's already true, it hopefully won't take much
convincing. :) If you mean to convince the
On 2003-01-07 at 11:31:13, Mr. Nobody wrote:
.length is unneeded, since an array gives its length in numeric context, so
you can just say +@a.
Unneeded, but harmless.
grep shouldn't be an array method either, it should be
like the perl5 grep, as it is often used on lists, grep /foo/, keys %h
On 2003-01-16 at 11:41:56, Dan Sugalski wrote:
And keyboards, don't forget keyboards. These pesky primitive ones we
have now would require a lot of shift-control-alt-meta-cokebottle key
sequences...
Unicode may have thousands of characters, but how many of them do you
think you'll use often
Glad to see someone heeded that warning about unrecognizable sarcasm;
no danger of misinterpretation here . . . :)
On 2003-01-16 at 10:01:04, Michael Lazzaro wrote:
Well, I don't know about anyone else, but *I'm* planning on making
many, many Unicode synonyms, to make my code shorter and more
On 2003-01-16 at 16:42:15, Buddha Buck wrote:
[Note: I originally sent this to Mr. Nobody alone, but that wasn't my
intent. I'm re-sending it here, where I wanted it to go in the first
place. -- bmb]
This came in with a content type text/plain, charset=us-ascii.
US-ASCII is by definition 7
On 2003-01-17 at 19:00:04, Simon Cozens wrote:
This is plainly untrue. See the perlsub documentation, which talks about
creating your own syntax with the prototype. You can do all this in
Perl 5, and it saddens me that some of the people redesigning Perl don't
know what Perl can do.
Well, if
On 2003-01-17 at 14:15:46, I wrote:
But as I see it, the real problem being solved by the new syntax
is that grep and map can exist solely as methods on some class
in the inheritance tree of @arrays, no global functions required.
That is a Good Thing.
I realize that such also be true if we
On 2003-01-17 at 17:17:03, Joseph F. Ryan wrote:
But as I see it, the real problem being solved by the new syntax
is that grep and map can exist solely as methods on some class
in the inheritance tree of @arrays, no global functions required.
That is a Good Thing.
In your opinion.
On 2003-01-21 at 11:09:21, Thom Boyer wrote:
One of the most... er, *interesting*, dodges I've seen in this area is the
one used by Squeak (a Smalltalk variant). Squeak spells assignment with an
underscore (_), but the Squeak system *draws* it as a left-pointing arrow.
There's a history behind
On 2003-01-29 at 09:44:27, Aaron Sherman wrote:
Yes, I would expect that. In my opinion there is no difference between
an array and a hash other than the underlying storage and the
type-management of the key.
Perhaps it is your opinion that those should be the only differences,
but the actual
On 2003-01-29 at 10:32:58, Mark J. Reed wrote:
(What their value should be is the subject of the
parallel thread on array defaults).
Whups, that would be THIS thread, actually. The sidebar on
removing the syntactic distinction between arrays and hashes
made me think I was over in the Spare
On 2003-02-07 at 11:13:07, Austin Hastings wrote:
--- Michael Lazzaro [EMAIL PROTECTED] wrote:
I'm trying, and failing, to accurately and definitively answer the
question what's the difference between an array and a list in
Perl6?
How's this?
A list is a literal (e.g.,
On 2003-02-07 at 14:26:42, Mark J. Reed wrote:
Not really, though. A list can be an lvalue, provided it is a list
of lvalues:
($a, $b, $c) = 1,2,3;
Forgot the parens on the right side, there:
($a, $b, $c) = (1,2,3);
But they certainly aren't lvalues:
[$a,$b,$c
On 2003-02-07 at 12:18:21, Austin Hastings wrote:
Although this may reasonably be regarded as a special case; you
certainly can't pop a list:
(1,2,3).pop = error
But could you do it the other way (function instead of method)?
pop (1,2,3) = ?
Nope. At least, not in Perl
[Recipients trimmed back to just p6-language; the Cc: list was getting
a bit large.]
On 2003-02-11 at 12:56:45, Garrett Goebel wrote:
I'd just stick with Uri's explanation. Arrays are allocated. Lists are
on the stack...
Nuh-uh. Those are implementation details, not part of the language
On 2003-02-11 at 17:12:52, Joseph F. Ryan wrote:
(@a,@b,@c).pop
This doesn't make any sense, since pop modifies the pop-ee.
What do you expect should happen here?
[@a,@b,@c].pop
Same as above.
Except that the Perl5 equivalent, ugly as the syntax may be, works fine:
On 2003-02-11 at 17:44:08, Mark J. Reed wrote:
pop @{[@a,@b,@c]}
It creates an anonymous array, then removes the last element, leaving two
elements in the array - which is irrelevant since the array is
then discarded completely.
Minor correction: we don't know how many elements
On 2003-02-11 at 16:52:36, Dave Whipp wrote:
Mark J. Reed [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
On 2003-02-11 at 17:44:08, Mark J. Reed wrote:
pop @{[@a,@b,@c]}
It creates an anonymous array, then removes the last
On 2003-02-12 at 11:07:45, Joseph F. Ryan wrote:
Meaning that I think this should be possible, but I'm not
sure if that syntax is correct, because it would mean that
the arrayrefs would need to be their own class to allow
a method to be called on it.
No, they wouldn't, unless I'm missing
On 2003-03-10 at 18:03:12, Uri Guttman wrote:
this confuses me. sometimes i want a simple pass by value param which i
can modify locally in the sub. is this the same as the constant above?
No, that's the same as is copy.
--
Mark REED| CNN Internet Technology
1 CNN Center
On 2003-03-11 at 10:12:17, Damian Conway wrote:
Austin Hastings wrote:
It is explicitly stated that is rw on a slurpy parameter distributes
across all the components.
Is there some way of differentiating array of const vs. array of rw?
That is, creating a hash or array that can be
On 2003-03-13 at 05:44:09, Damian Conway wrote:
2- Yeah! ... umm, are we *paying* you for this?
Not any more. In fact, like Larry and several others on the design team,
I'm now paying for the privilege of doing it. ;-)
If the TPF isn't supporting you folks anymore, what's the best
way for
On 2003-06-16 at 17:48:58, Simon Cozens wrote:
% grep printf cvs/modules/**/*pm | wc -l
15
% grep -v printf cvs/modules/**/*pm | wc -l
15360
Well, 0.1% agreed, anyway.
Now, now, that's hardly a fair comparison. Maybe if you grepped for lines
that contain print but not printf, or
Is it possible with the new parameter declaration syntax to declare
a mandatory name-only parameter?
-Mark
On 2003-08-01 at 09:54:57, Dave Whipp wrote:
A junction on one element is almost always redundant, and can be cast
directly into the scalar that is its eigenstate. The only issue with doing
that is that certain junction methods might not be available. However, in
the case of a Cnone, an
On 2003-08-05 at 16:10:46, Dan Sugalski wrote:
At 1:02 PM -0700 8/5/03, Dave Whipp wrote:
Can I discriminate on parameter names using multi subs?
Nope. Named parameters don't participate in MMD.
1. I'm thinking MMD should be called something else when being applied
to multisubs rather
[Recipients trimmed back to just the list, because it had gotten very
silly. When replying to someone who's on the list, there's no need to
copy them personally, too; they just end up with duplicates. :)]
On 2003-09-15 at 09:21:18, Piers Cawley wrote:
Great. But will it also be possible to add
On 2003-11-25 at 18:17:04, Piers Cawley wrote:
aString replace: aPattern with: aString.
aString replaceAll: aPattern with: aString.
Stop! Stop that at once! No small talk; we're here for
serious discussions!
:)
Except... the second argument isn't strictly a string because it's
On 2003-11-26 at 12:13:39, chromatic wrote:
Consider Perl 5, where File::Find is a core module. While the interface
may have been nice in 1995 (though I doubt even that), it's been widely
regarded as awful for at least three years. It's likely never to be
removed from the core.
chromatic With Apocalypse 12 (soon!)
RobinBerjon how soon? :)
LarryWall here's the rough outline
[indicating that it's pretty soon indeed]
Cool! But now I'm a little confused - what happened to Apocalypses 8
through 11? :)
-Mark
Should Perl6::Slurp be added to Bundle::Perl6? Or is that not being kept
up-to-date?
--
Mark REED| CNN Internet Technology
1 CNN Center Rm SW0831G | [EMAIL PROTECTED]
Atlanta, GA 30348 USA | +1 404 827 4754
On 2004-03-13 at 09:02:50, Karl Brodowsky wrote:
For these guys Unicode is not so attractive, because it kind of doubles the
size of their files,
Unicode per se doesn't do anything to file sizes; it's all in how you
encode it. The UTF-8 encoding is not so attractive in locales that make
heavy
On 2004-03-16 at 00:28:32, Karl Brodowsky wrote:
Mark J. Reed wrote:
Unicode per se doesn't do anything to file sizes; it's all in how you
encode it.
Yes. And basically there are common ways to encode this: utf-8 and utf-16
(or similar variants requiring = 2 bytes per character
On 2004-03-20 at 22:32:18, Calle Dybedahl wrote:
You don't need Unicode display « and », just plain old ISO 8859-1.
They're characters number 171 and 187 there. And AFAIK every Emacs
version released in the past ten years handles ISO-8859-1 out of the
box. It's more likely that you're using a
Juerd: your message arrived in my inbox as an attachment due to a mail server
along the way not recognizing the charset value. It should be utf-8
with the hyphen, not utf8. Also for that reason all the non-ASCII
characters (like the Yen symbol) came through as '?' here.
Kara Perlistoj,
And
On 2004-03-26 at 08:16:07, Larry Wall wrote:
And say isn't in there because of APL or PHP. It's actually inspired
by something worse in Ruby.
Presumably by something worse you mean puts? Not a great name, to
be sure, but it does have a venerable tradition behind it. :)
I do like having an
On 2004-04-13 at 13:16:02, David Cantrell wrote:
Perl 6, we are promised, will try to run legacy code unchanged. How
will it spot such legacy code?
My understanding has been that perl6 will assume a program is Perl 5 unless
it sees a Perl 6 keyword such as 'module' or 'class'.
--
Mark
Scott * %hash`s is an example of a small thing that would be easy to implement
Scott in core but would be used constantly (if JavaScript is any indication,
Scott every few lines), giving a lot of bang for the buck
Not sure that JavaScript is relevant here, since the equivalent
syntax there, .,
On 2004-04-15 at 16:49:28, Mark J. Reed wrote:
Not sure that JavaScript is relevant here, since the equivalent
syntax there, ., is the same as the method call syntax. But see my
proposal below.
Before the nit-pickers jump in, I was oversimplifying above. The
method call syntax in JavaScript
On 2004-04-15 at 19:39:25, Austin Hastings wrote:
Of course you used for buffers that were not powers of 2. Had they
been powers of 2, you would have used or ~. The fact that you
didn't use a power of 2 is pretty questionable. The dread Unix
wizards will no doubt have questions for you about
On 2004-04-16 at 00:25:51, Brent 'Dax' Royal-Gordon wrote:
Number of keystrokes isn't our only concern here. This is Perl, not
APL--we care about the size of the language and its intuitiveness too.
(Perhaps not much, but we do.)
In any case, Perl is far more typable than APL unless you have
On 2004-04-16 at 09:23:44, Mark J. Reed wrote:
On 2004-04-15 at 19:39:25, Austin Hastings wrote:
Of course you used for buffers that were not powers of 2. Had they
been powers of 2, you would have used or ~. The fact that you
didn't use a power of 2 is pretty questionable. The dread Unix
On 2004-04-16 at 11:17:41, Austin Hastings wrote:
I'm totally willing to agree with you, Mark.
A) Do you code hashing algorithms so frequently that you need a special,
low-cost-of-access operator built in to the language to support it?
Nope. I'd be perfectly happy if the modulus operator
On 2004-04-16 at 08:50:38, Brent 'Dax' Royal-Gordon wrote:
Mark J. Reed wrote:
Nope. I'd be perfectly happy if the modulus operator were spelled mod
instead of %, which has never struck me as particularly intuitive.
I always saw it as being a funny division sign. See the little slash
Let me just chime in with my support for John's basic idea. I would
definitely prefer that it be easy to arrange things such that
$obj.foo = 'bar'
winds up invoking a method on $obj with 'bar' as an argument, rather
than invoking a method on $obj that returns an lvalue to which
'bar' is
On 2004-04-20 at 10:51:47, Luke Palmer wrote:
I guess I bogged down that message with the implementation, so the
result may have been easy to miss.
That is what happened in my case. Apologies; it looks like your
original solution would do the job nicely. As long as the requisite
module comes
On 2004-04-20 at 11:37:18, Larry Wall wrote:
So do whatever you like to the declarations, but make sure you preserve
the symmetry and extensibility of
$obj.foo([EMAIL PROTECTED], *%NONSENSE) # get value of $.foo
$obj.foo([EMAIL PROTECTED], *%NONSENSE) = 5 # set $.foo
1 - 100 of 407 matches
Mail list logo
