On Thu, 10 Aug 2000 05:03:38 +0200, Bart Lateur wrote:
[description of a mechanism for storing sparse arrays:]
>Imagine
>that it will be traversed based upon the groups of bits in the array
>index. Say, with 32 bit indices, subdivided into 4 bytes. You can start
>with the lower byte, which can g
Piers Cawley <[EMAIL PROTECTED]> writes:
> Damian Conway <[EMAIL PROTECTED]> writes:
>
> >> Are the two values of a pair restricted in anyway? All your examples
> >> were scalar.
> >
> > Yes. The two components must be scalars.
> > The key is stringified iff it's a bareword.
> > Otherwis
I like the idea of currying, it seems powerful and Perlish in many ways.
However, I don't like the currying operator chosen, because of it's ugliness
(IMHO), and its potential for ambiguity (human, not necessarily parser).
So, here is my proposal to change the operator.
from to
---
> Proposal to rename C and C
The problem with this is that they rely on the indirect object notation,
same as new(). So:
import Module; # calls Module->import
new Module;# calls Module->new
bob Module;# calls Module->bob
So import and unimport aren't really specia
Mike-
Jeremy's got a great explanation of this, which I'll paraphrase, but the
discussion went through lots of iterations. Think of the ^ as a carat or
thumbtack, holding the place for later variables. Then, consider the
parallels:
Placeholder Variable
Anonymous ^_
On Fri, Aug 11, 2000 at 02:52:32AM -0700, Nathan Wiger wrote:
> Jeremy's got a great explanation of this, which I'll paraphrase, but the
> discussion went through lots of iterations. Think of the ^ as a carat or
> thumbtack, holding the place for later variables.
Yea, I ran across the description
[cc'ed on internals as FYI]
> =item 36 (v1): Structured Internal Representation of Filenames
I think this should be discussed a good amount. I think URIs are cool,
but too much trouble for simple stuff. I don't want to have to write
"file:///etc/motd" everytime I want to address a file. Too cumb
