>
> $$STDIN # Return one element regardless of context.
> @$STDIN # Return number of element wanted by context.
> *$STDIN # Return all element regardless of context.
>
How about
$STDIN.$ # Return one element regardless of context.
>That's a fine answer, but a completely different concern.
Sorry, you are correct. I looked up the RFC (there are getting to be so many
I cannot trust memory any more).
What I am thinking of is a file that, if present and sane (i.e. read-only
root), would be involked by the interpreter just bef
>I entreat you to explain to me *anything* that you'd want to tweak
>with this that you already can't do right now.
When I need to move Perl files from a default location to a new one. For
example messing with @INC (and its like). THis could be used for example on
a machine that has both develop
>>I'll second that motion. We already have lots of ways of removing the
>>last character of a string if that's what we really need.
>But they're slow and hard to read.
I would actualy like to see chop expanded to allow a variable number of
characters to be removed and a sister function to cut
>>I'd like to see every number bundled with a "precision" attribute.
>That's not what I call a high-level language feature. People don't
>want to think about that, nor about machine-level precision issues.
>See REXX.
>In fact, I'd rather to see a painless and transparent int->float->bignum
>
mailto:[EMAIL PROTECTED]]
Sent: Monday, August 14, 2000 2:15 PM
To: Lipscomb, Al
Cc: '[EMAIL PROTECTED]'
Subject: Re: RFC 89 (v2) Controllable Data Typing
> Having methods and properties on the basic data types seems like a nice
> thing.
>
> Just a thought.
Check out RFC'
lto:[EMAIL PROTECTED]]
Sent: Monday, August 14, 2000 1:40 PM
To: Lipscomb, Al
Cc: '[EMAIL PROTECTED]'
Subject: Re: RFC 89 (v2) Controllable Data Typing
On Mon, Aug 14, 2000 at 01:27:11PM -0400, Lipscomb, Al wrote:
> With some of the other suggestions to improve the "object" m
With some of the other suggestions to improve the "object" model in Perl I
was wondering if this would not be the time to ask about object-like
behavior around the simple scalar things.
For example if we had something like this:
my $id;
$id = "007";
print "My ID is $id->string\n";
Having meth
Not a bad solution, at least for the example I put forth. I like the ability
to have the specific as well as the general in the case statement ('2' and
'__%2 != 0'). Thanks.
> Could a way be found to control the flow so that the next case (not
always
> the one next in the order of the stat
Could a way be found to control the flow so that the next case (not always
the one next in the order of the statment) could be executed? For example
you have cases 1-10. You want all odd cases to also execute case 9 and the
even cases to also execute case 10. So in case 3 you would say something
l
10 matches
Mail list logo
