> hash slices aren't used much at all.
People *always* overgeneralize.
On Mon, May 13, 2002 at 05:48:17PM -0700, Ask Bjoern Hansen wrote:
> On Wed, 8 May 2002, Nathan Torkington wrote:
>
> Larry's State of the Onion slides from TPC5 are now available from
>
> http://dev.perl.org/perl6/talks/
> http://dev.perl.org/perl6/talks/onion5.pdf
Better sooner than never
On Tue, Jul 10, 2001 at 09:45:19PM +0200, Paul Johnson wrote:
> On Mon, Jul 09, 2001 at 11:46:30PM -0500, Jarkko Hietaniemi wrote:
>
> >
> >
> > XML
> > is
> > much
> > too
> > verbose
>
> And it should be neither written nor
> do
>
> s%([A-Z]+)([BE])%<${\(($2 eq 'E')?'/':'')}$1>%g
>
> on that and you've almost got XML!
XML
is
much
too
verbose
.
--
$jhi++; # http://www.iki.fi/jhi/
# There is this special biologist word we use for 'stable'.
# It is 'dead'. -- Jack Cohen
On Mon, Jul 02, 2001 at 01:30:11PM -0700, Damien Neil wrote:
> On Mon, Jul 02, 2001 at 12:59:51PM -0700, David Whipp wrote:
> > Its not quite the same thing, but Java does have the concept of
> > anonymous classes (it names them 'inner' classes): Is Perl6 going
> > to have a similar concept?
>
>
On Thu, Jun 21, 2001 at 11:49:21PM +0100, Simon Cozens wrote:
> On Thu, Jun 21, 2001 at 10:31:22PM +0100, Graham Barr wrote:
> > We can have a huge thread, just like before, but until we see any kind
> > of update from Larry as to if he has changed his mind it is all a bit
> > pointless.
>
> For
Maybe I missed it... but what is the relationship of (Perl 5) attributes
and Perl 6 properties?
my $answer : constant = 42;
my $answer is constant = 42;
my sub ... dang, no lexical subs, but can we please have them
in Perl6? :-)
sub terfuge : loc
> The statement I read was "true in any possible way", which implies that
> if $retval had a "true" property, the result of func would be
> irrelevant, since if func gave 0, "any possible way" would see the
> "$retval is true" property and take the "it worked" route.
>
> Thus, this code:
>
> my
On Fri, May 18, 2001 at 06:22:10AM -0700, Austin Hastings wrote:
>
> --- Damian Conway <[EMAIL PROTECTED]> wrote:
>
> > It's probably just a matter of coding what you actually mean.
> > In Perl 5 and 6 your version means "if $fh is true in *any*
> > possible way...", whereas you seem to want
> or some such, unless the purpose of the local(*foo) could be determined
> by unscrupulous means. Similarly, glob aliases *foo = *bar would
> need special treatment.
By far most of my use of typeglobs is making aliases, and then mostly
for code:
*color = \&colour;
So naturally I hope
On Thu, May 10, 2001 at 12:43:13PM -0500, David L. Nicol wrote:
> John Porter wrote:
> >
> > Larry Wall wrote:
> > >
> > > : do you think conflating @ and % would be a perl6 design win?
> > >
> > > Nope, I still think most ordinary people want different operators for
> > > strings than for number
On Sun, May 06, 2001 at 10:10:24PM +0200, Bart Lateur wrote:
> On Sat, 5 May 2001 15:22:40 -0700, Nathan Wiger wrote:
>
> > I suggest
> >that we simply create another q-op to do the qw-ish things you're proposing.
> >Perhaps qi() for "interpolate" or something else.
>
> qqw
Why I'm remind
On Sun, May 06, 2001 at 11:51:27AM -0700, Peter Scott wrote:
> At 08:33 AM 5/6/01 -0500, Jarkko Hietaniemi wrote:
> >On Sun, May 06, 2001 at 01:31:17AM -0600, Dan Brian wrote:
> > > For your collective amuse() abuse() dismiss() I humbly submit:
> > >
>
On Sun, May 06, 2001 at 08:33:45AM -0500, Jarkko Hietaniemi wrote:
> On Sun, May 06, 2001 at 01:31:17AM -0600, Dan Brian wrote:
> > For your collective amuse() abuse() dismiss() I humbly submit:
> >
> > "duran" (or derivatives)
> >
> > Aside from con
On Sun, May 06, 2001 at 01:31:17AM -0600, Dan Brian wrote:
> For your collective amuse() abuse() dismiss() I humbly submit:
>
> "duran" (or derivatives)
>
> Aside from conjuring images of "reflex", "rio", and maybe "Barbarella"
> for a select few, the word occurs in some interesting contexts.
On Fri, May 04, 2001 at 09:47:18AM -0600, Nathan Torkington wrote:
> Michael G Schwern writes:
> > "$foo has true" doesn't flow as well as "$foo is true". Dunno quite
> > what the other expected uses are.
>
> $foo has truth; # :-)
>
> This leads naturally to:
>
> $foo has the_buddha_natur
> Memory limits we should be able to do, assuming Perl 6 continues to
> have its own malloc.
Well... Perl doesn't use it's own malloc *that* widely. E.g. Linux
doesn't, since at least 5.005_03. FreeBSD doesn't. OpenBSD doesn't.
Darwin doesn't. AIX doesn't. IRIX doesn't. Starting from 5.8.0
On Wed, May 02, 2001 at 05:22:26PM -0400, David Grove wrote:
> > > am seeing some similarities between some of the proposed goals of
> > > Perl 6 and the .NET platform.
> > > . . . many things in .NET have been discussed similarly here.
> >
> > That's because .NET attempts to address real-world is
On Wed, May 02, 2001 at 05:36:11PM +0100, Graham Barr wrote:
> On Wed, May 02, 2001 at 06:29:51PM +0200, Bart Lateur wrote:
> > On Wed, 2 May 2001 17:05:31 +0100, Graham Barr wrote:
> >
> > >wantarray-ness is already passed along the call stack today. Thats
> > >the whole point of it. So what is
On Fri, Apr 27, 2001 at 02:28:58AM +0100, Simon Cozens wrote:
> On Thu, Apr 26, 2001 at 06:25:03PM -0500, Jarkko Hietaniemi wrote:
> > In a sick way I kinda liked how compilers were able to give out error
> > messages not unlike:
> >
> > foo.ada: line 231: Violation
On Thu, Apr 26, 2001 at 04:13:30PM -0700, Larry Wall wrote:
> Eric Roode writes:
> : John Porter wrote:
> : >IIUC, this ability is precisely what Larry was saying Perl6 would have.
> :
> : I may have my history wrong here, but didn't Ada try that?
>
> Not at all. The syntax of Ada was nailed do
On Tue, Apr 24, 2001 at 01:42:43PM -0700, Nathan Wiger wrote:
> Uri Guttman wrote:
> >
> > on the other hand, i use .= all the time and wouldn't like to lose
> > it. schwern idea of ce doesn't work for me as only the op= stuff means
> > assignment and ce would break that (e for = isn't visual eno
I think the magical "+" isn't going to work.
Has the road of just putting things next to each other been extensively
tried? It works for Awk... "juxtapose", the Famous Invisible Perl
Operator.
Perl 5 Perl 6
$a = $b . $c; $a = $b $c; # or $b$c
> Or we change the concatenation operator.
>
> $a = $b & $c; # Do people really use Perl for bit fiddling?
Oy! You keep your greedy fingers off my bitvectors.
(Incidentally I hope that in Perl 6 there's a way to shift the bitvector
aspect of $s: currently $s << and $s >> to shift the numeric
I don't get it.
The first and foremost duty of Perl 6 is to parse and execute Perl 6.
If it doesn't, it's not Perl 6. I will call this the Prime Directive.
I think as the first approximation the implementation of Perl 6 should
get that "simple" task right. If it doesn't, all our talk and work
On Tue, Apr 10, 2001 at 09:28:29AM -0400, John Porter wrote:
> Dan Sugalski wrote:
> > > if (-M "http://www.perl.com/" < -M "http://www.python.org/") {...}
> >
> > Nope. Doesn't work with other magic filenames, why should it with these?
>
> Because Perl6 will be better than Perl5.
> I wouldn't
http://www.zdnet.com/intweek/stories/news/0,4164,2705101,00.html
http://www.curl.com/html/technology/documentation.jsp
(and you have to admit the name is amusingly close)
--
$jhi++; # http://www.iki.fi/jhi/
# There is this special biologist word we use for 'stable'.
# It is 'dea
On Fri, Apr 06, 2001 at 08:42:18PM +, [EMAIL PROTECTED] wrote:
> Jarkko Hietaniemi <[EMAIL PROTECTED]> writes:
> >> But the structure you speak of exists only on the server. A URL as
> >> accessor reference doesn't really need to know anything about the open
On Fri, Apr 06, 2001 at 03:37:35PM -0400, Adam Turoff wrote:
> On Fri, Apr 06, 2001 at 03:31:56PM -0400, John Porter wrote:
> > Jarkko Hietaniemi wrote:
> > > So URLs are not
> > > literals, they have structure, and only thinking of them as filenames
> > >
On Fri, Apr 06, 2001 at 01:19:30PM -0600, Dan Brian wrote:
> > > > It might even mean that we can have a URL literal type,
> > >
> > > I trust that you will think long and hard about that.
> >
> > Agreed. Saying "URL literal type" is rather bold since "URL" is an
> > open-ended story. It is c
On Fri, Apr 06, 2001 at 07:57:28PM +0100, Simon Cozens wrote:
> On Fri, Apr 06, 2001 at 07:55:26PM +0100, Graham Barr wrote:
> > Ah OK. So I assume that
> > do "you";
> > will do the file in a void context
>
> Theoretically, yes. (ie, probably not.)
>From bleadperl t/op/do.t:
if (open(DO, ">
> > It might even mean that we can have a URL literal type,
>
> I trust that you will think long and hard about that.
Agreed. Saying "URL literal type" is rather bold since "URL" is an
open-ended story. It is certainly nice to think of them as opaque
filenames for "opening" them and doing IO
On Wed, Apr 04, 2001 at 11:46:12PM -0700, Nathan Torkington wrote:
> Not a comment at all on it? Was I accidentally unsubscribed to
> perl6-language?
>
> *tap* *tap* is this thing on?
>
> Nat
Me, I've been racking my brain to figure out whether Damian is Famine,
War, Plague, or Death...
--
$
On Thu, Mar 29, 2001 at 11:29:16AM -0500, Dan Sugalski wrote:
> At 05:19 PM 3/29/2001 +0100, Dave Mitchell wrote:
> >Jarkko Hietaniemi <[EMAIL PROTECTED]> wrote:
> > > Somewhat tangentially: this reminds me of a message a week ago or so
> > > (can't find
On Thu, Mar 29, 2001 at 10:25:06AM -0500, James Mastros wrote:
> On Wed, Mar 28, 2001 at 03:41:42PM -0800, Hong Zhang wrote:
> > Are we over-optimizing? The Perl is just an interpreter language.
> > Who really needs this kind of optimization for Perl? Even C does
> > not provide this feature.
> U
Nicely put, Merijn.
Stomping into (any) programming language camp and telling loudly that
what you are doing is wrong is a bit like stomping into a Mongol camp
and asking what's up with the funny fur hats.
Or, in the of case Perl, accusing us of too much line noise and being
too hard to read, is
> >A study in Science (291
> >P.2165) found out that
> >english speaking children has
> >twice as much reading
> >problems as italian speaking
> >children of the same age.
> >And about similar difference
> >towards german and french.
> >This could come from the
> >fact that english has for 40
> >p
On Mon, Mar 26, 2001 at 05:29:24PM -0500, John Porter wrote:
> Jarkko Hietaniemi wrote:
> > ST (or GR) applies to any situation where you your sort
> > comparator function isn't directly expressible with (Perl) primitives,
> > and worthwhile it is (like Yoda feel I) w
On Mon, Mar 26, 2001 at 05:17:38PM -0500, John Porter wrote:
> Simon Cozens wrote:
> > With all due respect, that's not been my experience. Even beginners know
> > how to do things like "length", by far the most common case for the ST.
>
> You must be kidding. Sorting a list of strings by length
On Wed, Mar 21, 2001 at 10:24:05AM -0500, John Porter wrote:
> Uri Guttman wrote:
> > records can be strings, or any perl [LH]o[LH].
>
> y/L/A/;
>
>
> > for a schwartz (drop the 'ian') or GR transform.
>
> Why? So it conforms with the "Guttman-Rosler" naming standard?
Which *I* would call
>What is this talk of software 'releases'? Klingons do not 'release' software;
>our software ESCAPES, leaving a bloody trail of designers and quality
>assurance people in its wake!
Sorry, forgot the annotation:
-- seen as the .sig of Malcolm Purvis <[EMAIL PROTECTED]>,
used completely without
What is this talk of software 'releases'? Klingons do not 'release' software;
our software ESCAPES, leaving a bloody trail of designers and quality
assurance people in its wake!
--
$jhi++; # http://www.iki.fi/jhi/
# There is this special biologist word we use for 'stable'.
# It
On Sat, Feb 17, 2001 at 08:53:51PM -0800, Russ Allbery wrote:
> So since when did perl6-language become perl-advocacy? Rephrased: Could
> people please take the advocacy traffic elsewhere where it isn't noise?
> Thanks.
Methinks trolls can't read.
--
$jhi++; # http://www.iki.fi/jhi/
#
>FOR
>---
> 1. It becomes more consistent with other Perl functions
my is not a function. It is a declaration. Functions take arguments
and return values. my does not. It is language construct like if.
Unless, of course, you claim that if is a function, too. That
ways lies LISP.
> Related
>
> Jarkko would really like
>
> print "Foo\n";
>
> in a void context to behave as
>
> print "Foo\n" or die $!;
Not just basic I/O but anything 'system': pipe(), system(), opendir(),
mkdir(), chdir(), fork(), socket(), and so on.
> I think that it would be nice in 5.8 to (optio
On Mon, Feb 12, 2001 at 02:41:01PM -0500, [EMAIL PROTECTED] wrote:
> Oh, I fully realize that *none* of this "self-extracting" nonsense is
> going to be cross-platform by any means. For each variation of Unix
Whew! I was starting to think I'm surrounded by tunnel visioned penguins.
> you'll ne
On Mon, Feb 12, 2001 at 02:19:54PM -0500, [EMAIL PROTECTED] wrote:
> On Mon, Feb 12, 2001 at 01:03:31PM -0600, Jarkko Hietaniemi wrote:
> > The problem of unpacking, or in other words, installing, or in other
> > words, embedded hardwired paths is hard. Think library paths: bot
> par can do something similar. It can slap a copy of pun (and thus
> perl) onto the archive. Its not simple, and its platform dependent,
> but its useful. I'm more and more seeing par as a way of
> embrace/extend/destroying perl2exe.
>
> And I think we could squeeze something into 5.8.
Caref
On Mon, Feb 12, 2001 at 12:36:53PM -0300, Branden wrote:
>
> John Porter wrote:
> > Branden wrote:
> > >
> > > For example, with tgz it would be complex to deal
> > > with running without extracting,
> >
> > What? tar -z not good enough for you?
> >
>
> The problem is that we cannot access indi
On Fri, Feb 09, 2001 at 09:22:13PM +, Nicholas Clark wrote:
> On Fri, Feb 09, 2001 at 02:53:43PM -0600, Jarkko Hietaniemi wrote:
> > On Fri, Feb 09, 2001 at 06:46:26PM -0200, Branden wrote:
> > > problems (like `oh! I don't have bzip2 and the developper only supplied a
On Fri, Feb 09, 2001 at 09:18:55PM +, Nicholas Clark wrote:
> On Fri, Feb 09, 2001 at 04:07:51PM -0500, John Porter wrote:
> > Branden wrote:
> > >
> > > For example, with tgz it would be complex to deal
> > > with running without extracting,
> >
> > What? tar -z not good enough for you?
>
On Fri, Feb 09, 2001 at 04:09:28PM -0500, John Porter wrote:
> Jarkko Hietaniemi wrote:
> > >
> > > (for those of you who didn't get the reference)
> >
> > Well, I certainly heard the reference before even hearing of Perl or Tom...
>
> I only eve
On Fri, Feb 09, 2001 at 04:05:54PM -0500, John Porter wrote:
> Jarkko Hietaniemi wrote:
> >
> > There isn't a software problem another abstraction layer can't fix...
>
> "...except the problem of too many layers of abstraction". tchrist
>
> (for t
On Fri, Feb 09, 2001 at 06:46:26PM -0200, Branden wrote:
> Jarkko Hietaniemi wrote:
> > Whatever we do I would much prefer being package format agnostic
> > instead of tying ourselves too tightly with some single format.
> >
>
> Any ideas on how to do that? Without br
On Fri, Feb 09, 2001 at 06:17:34PM -0200, Branden wrote:
>
> I had the time to do a research in Internet about rpm/jar. The correct URLs
> are:
> * http://www.rpm.org
> * http://java.sun.com/products/jdk/1.1/docs/guide/jar/
>
> I found great utilitaries in http://www.rpm.org/software.html, we co
On Tue, Feb 06, 2001 at 05:01:03AM +1100, Damian Conway wrote:
>> Really? Are lexicals in the sub visible in the post handler?
>
> No. Only the original arguments and the return value.
>
>> (Of course I realize *F does not illustrate this...)
>
> Exactly. ;-)
>
> Actually, I do agr
On Fri, Feb 02, 2001 at 03:54:33PM -0500, John Porter wrote:
> Jarkko Hietaniemi wrote:
> > > I rather like the idea that contract names are themselves namespace
> >
> > I rather dislike it: I think we are trying to stuff to much information
> > on the package names
> I rather like the idea that contract names are themselves namespace
I rather dislike it: I think we are trying to stuff to much information
on the package namespaces.
> names. A contract version's name is thus defined within that
> contract's namespace.
>
> E.g.
> "specifies Foo::Bar"
On Fri, Feb 02, 2001 at 02:57:20PM -0500, James Mastros wrote:
> On Fri, Feb 02, 2001 at 01:47:29PM -0600, Jarkko Hietaniemi wrote:
> > A DNS name is assuming too much about the organizational
> > structure and a mile long hex digit isn't very friendly, and neither
> > o
On Fri, Feb 02, 2001 at 02:36:43PM -0500, James Mastros wrote:
> On Fri, Feb 02, 2001 at 01:17:35PM -0600, Jarkko Hietaniemi wrote:
> > What I think is needed is some sort of opaque tag: the name of the
> > 'contract' the API claims to fulfill. The name can be the name
> >I wasn't clear. I was thinking that somehow a module would register with
> >the core what interfaces it support when it is installed. Anything else
> >is madness (ok, my idea is madness too).
>
> Your idea's not madness--it is, in fact, what I'm looking for us to define.
A gut feeling that
On Thu, Feb 01, 2001 at 04:54:53PM +, Simon Cozens wrote:
> On Thu, Feb 01, 2001 at 11:52:37AM -0500, Dan Sugalski wrote:
> > > just a method for doing what we currently do with, say, glob or
> > >the heavy unicode things?
> >
> > None of the above. What I'm looking for is the pieces that tu
On Wed, Jan 31, 2001 at 05:35:03PM -0500, Michael G Schwern wrote:
> On Wed, Jan 31, 2001 at 05:23:43PM -0500, Dan Sugalski wrote:
> > Pulling out or mangling time strikes me as intensely pointless, and I don't
> > see it happening. The socket stuff is really the only core functionality
> > that
On Wed, Jan 31, 2001 at 04:25:46PM +0100, Bart Lateur wrote:
> On Wed, 31 Jan 2001 08:53:13 -0600, Jarkko Hietaniemi wrote:
>
> >So nice of you to volunteer for being our help desk person man for
> >explaining to people why their time() just got broken :-)
>
> I'd u
On Wed, Jan 31, 2001 at 09:47:59AM -0500, James Mastros wrote:
> On Wed, Jan 31, 2001 at 09:53:23AM -0200, Branden wrote:
> > Because with a better built-in that handles fractions of second (if that's
> > ever desired, and I guess it is), time() would be deprecated and could
> > be easily reproduc
On Wed, Jan 31, 2001 at 09:49:59AM -0500, Andy Dougherty wrote:
> On Wed, 31 Jan 2001, Bart Lateur wrote:
>
> > On Tue, 30 Jan 2001 21:39:25 +0100, [EMAIL PROTECTED] wrote:
> >
> > >Why the urge to move it out of the core? Should perl6 be like Python,
> > >where you first need to do a gazillion
On Tue, Jan 30, 2001 at 02:09:32PM -0200, Branden wrote:
> Jarkko Hietaniemi wrote:
> > I guess it's part of the can of sub-second worms: if we do sleep(),
> > people will ask why don't we do time() and alarm(), too. sleep() and
> > alarm() we could get away with
On Tue, Jan 30, 2001 at 04:13:39AM -0500, Michael G Schwern wrote:
> Is there any really good reason why sleep() doesn't work for
> microseconds? I mean, if I can do this:
>
> sub sleep {
> my($time) = shift;
> if( /^[+-]?\d+$/ ) {
> sleep($time);
> }
>
On Sun, Jan 28, 2001 at 11:07:10PM -0700, Nathan Torkington wrote:
> Jarkko Hietaniemi writes:
> > > True, but you can't do any of all that without knowing the platform
> > > accurately (nontrivial and requires core mod or XS). Once that's
> > > done, the
On Mon, Jan 29, 2001 at 01:08:21AM -0500, Michael G Schwern wrote:
> On Sun, Jan 28, 2001 at 11:54:13PM -0600, Jarkko Hietaniemi wrote:
> > The desire to know the name of the runtime platform is a misdirected desire.
> > What you really want to know is whether function Foo will
On Sun, Jan 28, 2001 at 08:56:33PM -0500, Michael G Schwern wrote:
> On Sun, Jan 28, 2001 at 10:07:55PM +0100, Bart Lateur wrote:
> > Uhm, I'm sorry, but that's not good enough. You cannot distinguish
> > between Windows 95/98/ME on one side, and NT/2k on the other, using $^O
> > alone. After all,
I like the final point:
> Stay tuned, I'm sure I'll have found something new to hate by tomorrow.
>
> (Well, that's how this document originally ended. But it's not true,
> because I'm back to hacking in C, since it's the still only way to
> ship portable programs.)
--
$jhi++; # http://www.iki.
> > Larry mumbled something like "implements" and "interface". So to say
> >
> > package Net::FTP::Foo implements Net::FTP;
> >
> > But I don't think, anybody wrote an RFC about the plan.
>
> I did. Or something like it. And I've got a couple of modules on CPAN
> (that I really must documen
On Fri, Jan 05, 2001 at 09:42:12PM -0500, Brian Finney wrote:
> generally speaking when you look a number and convert it into text you go through
> some simble steps
>
> say we start with this number
> 123,456,789
> first we divide into sets of three
> (123,000,000)+(456,000)+(789)
> then we expa
On Mon, Jan 01, 2001 at 02:04:25PM -0600, Jonathan Scott Duff wrote:
> On Fri, Dec 29, 2000 at 11:47:59PM -0600, Jarkko Hietaniemi wrote:
> > The sorting algorithm? Before 5.005 (I think...my memory is going)
> > vendors' quicksort, after that Tom Horsley's excellent
On Sat, Dec 30, 2000 at 05:31:29AM +, David L. Nicol wrote:
> Piers Cawley wrote:
> >
> > >"David L. Nicol" <[EMAIL PROTECTED]> writes:
> > > After reading Cawley's
> > > method, I wondered if using it we could make radix-sorts the
> > > default sort method.
> >
> > Er... the point behind ch
On Thu, Dec 28, 2000 at 03:43:21PM -0500, John Porter wrote:
> Dan Sugalski wrote:
> >
> >use sort qw(radix_sort);
> >sort \&radix_sort @data;
>
> Isn't that the slot where the comparison function goes?
> Maybe something more like this:
>
> use sort::radix_sort;
> sort @data; # magicall
On Wed, Dec 27, 2000 at 06:36:56PM -0600, David L. Nicol wrote:
>
> Is there a perl6 sort committee yet? AFter reading Cawley's
> method here, I wonder if using it we could make radix-sorts the
> default sort method.
Radix sorts are great if the data cooperates, radix sorts can really
fly in su
On Mon, Dec 18, 2000 at 11:33:36AM -0700, Nathan Torkington wrote:
> I just got off the phone with Larry. He's been laid up for three
> weeks with a trip to Japan followed by a virus from Japan. He's on
So Perl 6 will be...Ruby? :-)
--
$jhi++; # http://www.iki.fi/jhi/
# There is this
On Fri, Dec 15, 2000 at 04:30:59PM -0500, Sam Tregar wrote:
> On Fri, 15 Dec 2000, Jarkko Hietaniemi wrote:
>
> > Limbo, the systems programming language of Inferno, nee Plan 9, nee UNIX.
> >
> > http://www.vitavuova.com/inferno/papers/limbo.html
>
> What are you
On Fri, Dec 15, 2000 at 03:22:48PM -0600, Jarkko Hietaniemi wrote:
> Limbo, the systems programming language of Inferno, nee Plan 9, nee UNIX.
>
> http://www.vitavuova.com/inferno/papers/limbo.html
>
> (
> Found thorough the the recent /. link where a whole operating syst
Limbo, the systems programming language of Inferno, nee Plan 9, nee UNIX.
http://www.vitavuova.com/inferno/papers/limbo.html
(
Found thorough the the recent /. link where a whole operating system
(Inferno) is available as a browser (IE) plugin:
http://www.vitanuova.com/inferno/pidoc/index.ht
> * XS, the system for extending Perl with C or C++, will be replaced
> with something much easier to use. This will give people very
> convenient access to existing code libraries, and write C or C++
> subroutines that can be called as Perl subroutines from Perl code
> to take
> Any others? There are bugs in the RFC process. Now is the time to
> fix them.
I don't know whether this is worth a separate improvement # but here goes:
Too many RFCs live in a vacuum by not not explaining in enough detail
what is the problem they are trying to solve, but instead go ahead an
> I disagree. The RFC process is for generating ideas, not making decisions,
> nor is any author obliged to include ideas he/she doesn't agree with;
> that's why others can (or could) submit RFCs that contradict it, if they
> want to. The author is no more obliged to include opposing opinions
> > Status: Frozen
>
> I'm sorry, I was gonna bite my lip, but I've gotta say: Freezing RFC's
> like this when the following is true:
>
> > A lot of good, heated discussion was generated on the mailing lists. The
> > majority seems against using XML-DTD documentation, but granted there are
> >
On Mon, Oct 02, 2000 at 09:17:31PM -0500, David L. Nicol wrote:
> Jarkko Hietaniemi wrote:
>
> > This reminds me of a related but rather opposite desire I have had
> > more than once: a quotish context that would be otherwise like q() but
> > with some minimal extra typi
On Mon, Oct 02, 2000 at 07:32:42AM -0400, Bryan C. Warnock wrote:
> On Wed, 27 Sep 2000, Nathan Wiger wrote:
> > Yeah, I've never liked the _ syntax, I've always thought it was weird
> > (to say the least). I think grouping file tests would be much cleaner.
>
> As long as you are okay with havin
On Fri, Sep 15, 2000 at 01:56:39PM +1100, Damian Conway wrote:
>> Hang on... \I \E amounts to the same number of characters as using
>> '. .' (that is, terminating this q-string, concat the thing, start
>> a new q-string)
>
> You can't do that in a <<'HERE' doc.
True.
>> For
Hang on... \I \E amounts to the same number of characters as using
'. .' (that is, terminating this q-string, concat the thing, start
a new q-string) So for scalars, there would be no savings at all.
For arrays, yes, the proposed \I \E would still be useful. Maybe the
\I should just scan for t
On Thu, Sep 14, 2000 at 10:01:23PM -0400, Jerrad Pierce wrote:
> What's wrong with extending current syntax such that:
Please read the discussion so far.
--
$jhi++; # http://www.iki.fi/jhi/
# There is this special biologist word we use for 'stable'.
# It is 'dead'. -- Jack Cohen
On Fri, Sep 15, 2000 at 10:29:31AM +1100, Damian Conway wrote:
> Why not just give \I..\E a special "turn-on-interpolation" meaning in
> q{} docs?
>
> $code = '
>
>
> $x = $y;
> @a = (1..10);
> $name = \I$funcname\E;
That would be four keystrokes
On Thu, Sep 14, 2000 at 06:17:07PM -0400, Mark-Jason Dominus wrote:
>
> > > One could for example have a pragma to *really* tag variables
> > > lexically to be expanded within singlequotes.
>
> Or a pragma that simply changes the semantics of q{...} so that it has
> the proposed feature for th
On Thu, Sep 14, 2000 at 05:11:39PM -0500, Jarkko Hietaniemi wrote:
> On Thu, Sep 14, 2000 at 06:04:41PM -0400, Mark-Jason Dominus wrote:
> >
> > > seconded by Mark-Jason Dominus <[EMAIL PROTECTED]>
> >
> > Except that I don't think adding this feature
On Thu, Sep 14, 2000 at 06:04:41PM -0400, Mark-Jason Dominus wrote:
>
> > seconded by Mark-Jason Dominus <[EMAIL PROTECTED]>
>
> Except that I don't think adding this feature to the existing q{...}
> is a good idea. If I had to vote on your proposal, I would instantaly
> vote against it. I thi
On Thu, Sep 14, 2000 at 11:46:31AM -0400, 'John Porter' wrote:
> Jarkko Hietaniemi wrote:
> > > In the other camp, C has been suggested; but
> > > the conflation of that with its thread-related semantics may not
> > > be a such good idea.
> >
> David L. Nicol wrote:
> > "Randal L. Schwartz" wrote:
> > >
> > > I think we need a distinction between "looping" blocks and
> > > "non-looping" blocks. And further, it still makes sense to
> > > distinguish "blocks that return values" (like subroutines and map/grep
> > > blocks) from either o
On Wed, Sep 13, 2000 at 10:49:41PM +0200, Bart Lateur wrote:
> Imagine the following scenario: your script contains a doiuble-quotish
> 40 line here-doc, with a bunch of variables in it. Unforetunately, you
> forgot to set one, and you get the not so helpful complaint:
>
> use of unitialize
On Mon, Sep 11, 2000 at 05:31:33PM -0400, 'John Porter' wrote:
> Garrett Goebel wrote:
> >
> > I'd be surprised if
> >
> > sub mygrep (&@) {
> > my ($coderef, @list, @stack) = @_;
> > &$coderef and push(@stack, $_) foreach (@list);
> > return @stack;
> > }
> >
> > @a = mygrep { return (
> Exactly the sort of chicanery grep/last is meant to avoid. So the question
> becomes, how do we crowbar "last" in without altering the returned value in
> C blocks. I'm for putting it after a comma. Which matches the syntax of
> John Porter's proposal about internally converting the block to a
1 - 100 of 151 matches
Mail list logo
