Damian Conway [EMAIL PROTECTED] writes:
From a Perl 6 perspective, it seems likely that C%_ will be the name
commonly used for the slurpy hash of a subroutine. Just as C@_ will often
be the name used for the slurpy array. See Exegesis 6 for more details.
Indeed, when it comes to object
We have been discussing how to pass data to Tk callbacks.
In particular Entry widget validation routines.
There are a number of items that they _might_ be interested in
but a typical routine would only use a few.
Currently it passes them all as positional parameters.
One idea that occured to
(PERL_POLLUTE).
--
Nick Ing-Simmons
http://www.ni-s.u-net.com/
see any ESP there? Do you see any parsing of arbitrary pieces of
code? No, me neither.
--
Nick Ing-Simmons [EMAIL PROTECTED]
Via, but not speaking for: Texas Instruments Ltd.
Uri Guttman [EMAIL PROTECTED] writes:
"NI" == Nick Ing-Simmons [EMAIL PROTECTED] writes:
p5p removed
NI I have guts of a stack-of-layers PerlIO scheme coded now
NI (//depot/perlio/... for those with perforce access - merge to 5.7.0
NI will occur as soon a Jarrko likes.)
does
the one I like best - avoids the un-meritted assumption
it will be sunny ;-)
--
Nick Ing-Simmons [EMAIL PROTECTED]
Via, but not speaking for: Texas Instruments Ltd.
# $foo=1 $baz=2 @bar=(4)
Wouldn't that be $baz = 3, since the middle list would be taken in scalar
context?
Which has sanely become the length of the list rather than last element.
--
Nick Ing-Simmons
of widgets which are "toplevels" and thus should respond to methods
relating to the "Window Manager".
These "mixin" classes typically add extra methods which are defined in terms
of methods of the "core" object. As such they do not _usually_ require
attr
present both schemes to tanslate perl5 code
(but it can be "moderately awkward" to discourage new weirdnesses).
--
Nick Ing-Simmons
from native
in the UNIX case at least.
--
Nick Ing-Simmons
that the single-arg form of select() is the
one you're suggesting for deprecation, and not the four-arg form.
The 4 arg form will be deprecated somewhere else. Splitting the function
is a good idea...
--
Nick Ing-Simmons
John Porter [EMAIL PROTECTED] writes:
Nick Ing-Simmons wrote:
Ed Mills [EMAIL PROTECTED] writes:
There are many logical reasons for and against the RFC's here, but saying
"it looks like c so it doesn't make it for me" is a weak argument at best.
I don't think anyone made tha
to be nothing unique to
=. You
could just as well say
bareword, $whatever
and get the same effect in perl5!
Have you used strict lately? :-)
It also matters in this case:
sub bareword { }
foo(bareword,4);
vs
foo(bareword = 4);
--
Nick Ing-Simmons
ve "things" (scalars, arrays, hashes) will have 'vtables'
(table of functions that do the work). So in that sense an array as in @foo
can be an "object" at some level of meaning while not being an "object"
at the perl level.
--
Nick Ing-Simmons
is always inexact and incorrect - thats why we need NTP.
--
Nick Ing-Simmons
URI/URL syntax can perhaps dodge the "portability" issue
URLs use / so if user thinks URL they think /.
--
Nick Ing-Simmons
-"it's like this"---
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
--
Nick Ing-Simmons
Peter Scott [EMAIL PROTECTED] writes:
At 06:23 PM 8/9/00 +, Nick Ing-Simmons wrote:
Damian Conway [EMAIL PROTECTED] writes:
Operator overloading is scheduled to be revamped.
While I remember - it would be good if overload mechansim
could be extended to cover and ||
Yes.
as well
u cannot as far as I aware define new operators in C++ - just redefine the
ones you have. I cannot decide that '|' is now an operator.
I guess it's getting too incestuous with the lexer.
That is the root of the problem.
--
Nick Ing-Simmons
Dan Sugalski [EMAIL PROTECTED] writes:
At 11:40 AM 8/5/00 +, Nick Ing-Simmons wrote:
Damian Conway [EMAIL PROTECTED] writes:
It definitely is, since formats do things that can't be done in
modules.
Such as???
Quite.
Even in perl5 an XS module can do _anything at all_.
It can't
t straight?
At the perl level yes. The core C can push an AV * on the stack
but perl does not know what it means. (Tk did this for a while
internally before I decided to comply with the perl semantics.)
--
Nick Ing-Simmons
of years - all the serious
stuff was done in latin (or even french).
--
Nick Ing-Simmons
Michael Mathews [EMAIL PROTECTED] writes:
Jonathan Scott Duff said
Status: tabled # shelved, put away for now
Please avoid 'tabled' - it means near the opposite in the UK.
To table something is to put it "on the table" i.e. open for discussion.
--
Nick Ing-Simmons
;
for a while.
But I just realized if $ is one of something, @ sereral etc.
then do we need a magic char to designate 'type' (class or whatever).
I suppose:
my ¢Dog $spot; # That is "cent" i.e. c with line.
might do ;-)
--
Nick Ing-Simmons
often whant variables to cross {} boundaries,
if any mention of thing on left declares it in current scope you
end up with "upvar" and "global" to say "no I don't mean that".
--
Nick Ing-Simmons
ine still has locking issues if it updates "global" state.
--
Nick Ing-Simmons
.
Full ground-up rewrite, like sfio but Perlish.
I think that is almost a given - we have been on verge of doing it for
perl5 for years.
--
Nick Ing-Simmons
ny (or all) combinations of the above.
Please explain what the utility of having unshared variables?
Thread local storage - is often what you want most of.
I might
as well just fork().
That assumes you can fork() ...
chaim
--
Nick Ing-Simmons
+ perl.dll or .../bin/perl + libperl.so
perl distribution
anything from perl6.tar.gz
Optional module
things in CPAN
--
Nick Ing-Simmons
ointer to blue-white-hot "NoOp" function
which is near always in-cache, for a typed var it could be a slow
as you wanted...
--
Nick Ing-Simmons
30 matches
Mail list logo
