I believe Dan said that he wanted to make objects a lot faster in P6. I
don't think we should be precluded from requesting Things That Make Sense
(tm) just because the current implementation is sub-optimal in performance
if nothing inherently prevents a better implementation.
I don't
On Thu, Aug 24, 2000 at 02:09:15PM -0400, Chaim Frenkel wrote:
"JH" == Jarkko Hietaniemi [EMAIL PROTECTED] writes:
JH "The first operation done on the return value of open() shall be defined()
JH or you shall regret your pitiful existence."? (a flag on the scalar
On Sat, Aug 12, 2000 at 10:27:17PM -0400, Dan Sugalski wrote:
At 10:24 PM 8/12/00 -0400, Chaim Frenkel wrote:
"NW" == Nathan Wiger [EMAIL PROTECTED] writes:
NW just deal with filenames universally this would be a big win (leave
NW acls, permissions, versions, etc to something else).
On Wed, Sep 06, 2000 at 03:47:57PM -0700, Randal L. Schwartz wrote:
"Mark-Jason" == Mark-Jason Dominus [EMAIL PROTECTED] writes:
Mark-Jason I have some ideas about how to do this, and I will try to
Mark-Jason write up an RFC this week.
"You want Icon, you know where to find it..." :)
On Thu, Sep 07, 2000 at 03:42:01PM -0400, Eric Roode wrote:
Richard Proctor wrote:
I think what is needed is something along the line of :
$re = qz{ '(' \$re ')'
| \$re \$re
| [^()]+
};
Where qz is some hypothetical
Please give it a rest. I think everybody got it by now. Everybody
understands how the current implementation works and what the
semantics are, and you disagree with the current semantics. I think
that's the end of story since changing current default semantics is
simply not an option. We
More generally, it seems to me that you're hung up on the description
of "*?" as "shortest possible match". That's an ambiguous
Yup, that's a bit confusing. It's really "start matching as soon as
possible, and stop matching as soon as possible". (The usual greedy
one is, of course, "keep
The clue is "If a sub wants to return an lvalue, it must Bbe an
lvalue". Therefore I propose a new keyword Clreturn that behaves
just like Creturn, but returns the lvalue instead of the rvalue. After
returning, everything is exactly as if the argument to lreturn were
specified instead of the
I should read what has been said about the matter earlier...but
lacking the time, I'll just shoot:
What's wrong with stealing from C/C++/Java instead
of trying to invent our own?
In other words, what's wrong with /* ... */?
--
$jhi++; # http://www.iki.fi/jhi/
#
On Sun, Aug 06, 2000 at 04:40:29AM +1000, Damian Conway wrote:
Oh, the table thing. The switch statement is useful without learning the
complete table so I don't think complexity is a big problem. People can
learn what they need and ignore the rest. I agree with you that it might
I also confess to liking // more for till-end-of-line comment marker
than #, the hash looks so messy to my eye...of course, // already has
a meaning...
--
$jhi++; # http://www.iki.fi/jhi/
# There is this special biologist word we use for 'stable'.
# It is 'dead'. -- Jack Cohen
On Sun, Aug 06, 2000 at 06:37:12AM +1000, Damian Conway wrote:
The solution is simple: return hashes instead of lists.
I still think returning lists *or* hashrefs according to context gives
the same benefits *plus* backwards compatibility.
I sent v2 before I saw just suggestion...wait
On Sun, Aug 06, 2000 at 12:41:50AM +0300, Ariel Scolnicov wrote:
Jarkko Hietaniemi [EMAIL PROTECTED] writes:
[...]
Another alternative would be Javadoc / doxygen / ... style comments
(say #@ introduces a comment to be extracted).
Yuk. More magic to remember. Me hate.
What
Summary of manifesto: Global variables must be expunged.
Replacing the old rotten global variables with new rotten global
variables is not enough of an improvement.
Hurrah! clap clap clap stomp stomp stomp hats state="flying
(Same goes for package variables: $File::Find::name, anyone?
I agree with Tuomas' assessment. We would certainly love to dispense
with
the need for PDL if perl6 offered something along these lines.
But PDL is much more than an efficient memory representation for typed
N-D arrays. Above Jeremy suggests that most of the rest of the PDL core
is already
Whatever you do, don't use those timezone names. Is EST Eastern US time
or Eastern Standard Time in Australia? The same abbreviation is used in
both places.
Naming of time zones is a *huge* rathole that you probably just don't want
to crawl into. The short abbreviations are *not*
We will never conquer the world with Perl 6:
CobolScript(R) got there before us.
http://www.cobolscript.com/
--
$jhi++; # http://www.iki.fi/jhi/
# There is this special biologist word we use for 'stable'.
# It is 'dead'. -- Jack Cohen
On Thu, Aug 10, 2000 at 05:21:44PM +0300, Jason Elbaum wrote:
As far as I know, there is a basic bit of regexp functionality which
Perl should support but doesn't.
Perl regexps support the following features, though they're a bit
obscure to my tastes...
(from perlre:)
\l
On Thu, Aug 10, 2000 at 08:55:27AM -0700, Peter Scott wrote:
At 10:28 AM 8/10/00 -0500, Jarkko Hietaniemi wrote:
On Thu, Aug 10, 2000 at 05:21:44PM +0300, Jason Elbaum wrote:
As far as I know, there is a basic bit of regexp functionality which
Perl should support but doesn't.
Perl
On Thu, Aug 10, 2000 at 09:30:05AM -0700, Russ Allbery wrote:
Bart Lateur [EMAIL PROTECTED] writes:
As for the parameter's format: GMT is easy, you can pass "GMT" (or
"+"). For localtime(), you often don't explicitely know the time
zone and Daylight savings Time rule, so this looks
On Fri, Aug 11, 2000 at 02:09:43AM +0200, Bart Lateur wrote:
On Thu, 10 Aug 2000 14:39:39 -0500, Jarkko Hietaniemi wrote:
Did not.
people in Newfoundland are going to expect to be
able to pass in -0230 and have that work, and that's interestingly hard.
What's so hard? Subtracting 2
On Fri, Aug 11, 2000 at 10:06:38AM -0700, Nathan Wiger wrote:
I know other languages call it zip, but personally I dislike
that name as zip() is commonly used with reference to compression.
Ditto, I really dislike zip() and unzip(). They're PC and even UNIX
commands on several platforms
On Fri, Aug 11, 2000 at 04:48:12PM -0500, David L. Nicol wrote:
It's a vast and contrived joke, right?
If it is, someone has really gone into some trouble:
http://www.cobolscript.com/samples.htm
Jarkko Hietaniemi wrote:
We will never conquer the world with Perl 6:
CobolScript(R) got
I simply can't get over the feeling that the proposed
zip/unzip/partition functions are far too specialized/simple, and that
something more general-purpose in the order of pack/unpack (with the
transformation spec encoded in a template) for lists would be preferable.
When someone said that
Subject: Re: RFC 48 (v2) Replace localtime() and gmtime() with da
What keeps truncating the rfc subject lines?
On Fri, Aug 11, 2000 at 04:22:33PM -, Perl6 RFC Librarian wrote:
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Replace
On Sun, Aug 13, 2000 at 06:54:10PM +1000, iain truskett wrote:
* Jeremy Howard ([EMAIL PROTECTED]) [13 Aug 2000 17:28]:
[...]
Personally, I like 'weave' rather than 'zip'. I'm happy with 'unweave'
too--although I'm still unsure about that one...
Weave is too much like Knuth's tangle and
How 'bout 100ns ticks from base date, stored in a 64-bit number? That
We are going to have quads supported on all platforms, then? With
software emulation of our own if nothing else is available? I wouldn't
object, mind...
--
$jhi++; # http://www.iki.fi/jhi/
# There is this special
On Tue, Aug 15, 2000 at 11:31:50AM -0500, Adam Krolnik wrote:
Following the lead of the sort operator, it would be a little
simpler to see reduce expressions use $a and $b instead of
$_[0], $_[1].
The $a and $b of the sort comparator were A Bad Idea to begin with.
There's nothing wrong
On Tue, Aug 15, 2000 at 05:20:11PM -0400, John Porter wrote:
Dan Sugalski wrote:
The ultimate target of a program's source code is the *programmer*.
Programmers, being people (well, more or less... :), work best with symbols
and rich context. Stripping contextual clues out of code
On Wed, Aug 16, 2000 at 08:01:12AM +1000, Damian Conway wrote:
I don't think the :lvalue is needed. This isn't really an attribute - if
someone writes:
$r-name = 'Mithrandir';
there's no confusion that it's assigning it.
Ah, but there's definitely a confusion
(Yes, there is a small aesthetic edge in using $a vs $_[0], but I still
consider the $ and $b to be warts.)
And anyhow, this will work just fine (see RFC 23):
$sum = reduce ^a + ^b, @numbers;
I have been amply reminded of this, thanks :-) (Too little time
to spend on RFCs...)
--
On Wed, Aug 16, 2000 at 08:37:21AM +1000, Jeremy Howard wrote:
Stephen P. Potter wrote:
Lightning flashed, thunder crashed and John Porter [EMAIL PROTECTED]
whispered
:
| Here's a counter-proposal: throw out hashes as a separate internal
| data type, and in its place define a set of
No, neither proposal makes sense. Arrays can be stored compactly and
$a[1_000_000_000] = 'oh, really?' # :-)
my int @a: sparse;
I see: you have a time machine and I don't. So very unfair...
$a[1_000_000_000] = 'Yes, really!' # :P
OK, so I cheated... I haven't submitted my RFC
On Wed, Aug 16, 2000 at 09:49:36AM -0400, Stephen P. Potter wrote:
Lightning flashed, thunder crashed and Jonathan Scott Duff [EMAIL PROTECTED]
whispered:
| Um, it's not guaranteed to blow up in 2038. That's an implementation
| detail. IF we implement our time values as 64-bit integers
On Wed, Aug 16, 2000 at 04:41:33PM +0100, Graham Barr wrote:
On Wed, Aug 16, 2000 at 10:20:28AM -0500, Jonathan Scott Duff wrote:
m//gt would be defined to do the match, and return the count of matches, this
leaves all existing uses consistent and unaffected. /t is suggested for
On Wed, Aug 16, 2000 at 12:44:50PM -0400, John Porter wrote:
Jonathan Scott Duff wrote:
Gee, I'd hate to lose simple assignment to a hash from a list.
foo %= bar;
No, wait, that obviously leaves the modulus of division scalar foo by
scalar bar to foo... No, wait, tha obviously
This is one of the nice things about Python, in my opinion. Every
error is an exception, so you can feel free to completely ignore
Like end of file? :-)
Hmm. It just occurred to me that you could combine your idea with
exceptions quite nicely: All core functions throw exceptions on
Is Perl currently using different epochs on different platforms? If so, I
Yes. MacOS and VMS. (Though VMS' localtime() uses the UNIX definition,
just to be portable.) MacOS' epoch zero is 1900 (or was it 1901?),
VMS' epoch zero is 17-NOV-1858 00:00:00.00, for some astronomical
reason IIRC.
On Fri, Aug 18, 2000 at 03:46:10AM -0500, David L. Nicol wrote:
Mike Pastore wrote:
Any thoughts on this?
Yes, please, the idea, that is: I've wanted such a variable oftentimes.
What I'm not certain about is reusing the $#. Reusing obsoleted stuff
is Dangerous.
Attributes.
($item :
On Mon, Aug 21, 2000 at 03:43:44PM -0600, Tom Christiansen wrote:
dump FILE; # dump program state as opcodes
You don't like that that should be a checkpoint resurrection at the
point in the programmer labelled with "FILE:", per the current
(semi-dis-)functionality?
Isn't
On Tue, Aug 22, 2000 at 09:49:12AM -0400, John Porter wrote:
Damian Conway wrote:
Easy. I'll just add a Cthing operator to Q::S. It would take no
arguments and return a (lazy?) list of every possible Perl subroutine.
PS: Can you tell whether I'm joking?
I think you're both joking
On Thu, Aug 24, 2000 at 03:40:00PM -, Perl6 RFC Librarian wrote:
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Case ignoring eq and cmp operators
=head1 VERSION
Maintainer: Markus Peter [EMAIL PROTECTED]
Date: 24 Aug 2000
On Thu, Aug 24, 2000 at 10:28:51PM +0200, Bart Lateur wrote:
On 24 Aug 2000 15:40:00 -, Perl6 RFC Librarian wrote:
Perl currently only has Ceq and Ccmp operators which work case-sensitively.
It would be a useful addition to add case-insensitive equivalents.
Next you'll want
I want four special new comparison operators.
Firstly,
" e q "
That is, an operator that ignores any leading, any trailing, and treats
all intraspace as equivalent. If the embedded space is confusing, I may
consider suggesting an operator modifier, "/ ".
Secondly,
Eq,
which
: That numerical part could then form the basis of the extended exception
: mechanism. No, the programmer shouldn't memorize the error numbers:
: there should be predefined constants, like
:
: ERROR::filenotfound
:
: which are numeric, and which could then be used for the catch
On Wed, Aug 30, 2000 at 11:10:54AM -0400, John Porter wrote:
Snatch two syntax constructs away from the jaws of illegal syntax and
an unfortunate syntax, and make them useful weapons of the Perl
arsenal. The constructs are:
$ref-[[LIST]]
$ref-{{LIST}}
The proposed
On Wed, Sep 06, 2000 at 09:43:03AM -0500, Garrett Goebel wrote:
From: Jonas Liljegren [mailto:[EMAIL PROTECTED]]
Does any other RFC give the equivalent to an 'in' operator?
I have a couple of times noticed that beginners in programming want to
write if( $a eq ($b or $c or $d)){...}
On Wed, Sep 06, 2000 at 09:46:13AM -0600, Tom Christiansen wrote:
grep { $_ == 1 } 1..1_000_000
grep doesn't short-circuit.
I never did figure out why "last" {w,sh,c}ouldn't be made to do
that very thing.
Agreed, that would be very natural.
--
$jhi++; # http://www.iki.fi/jhi/
On Thu, Sep 07, 2000 at 10:05:58PM +0200, Bart Lateur wrote:
On Fri, 8 Sep 2000 05:59:02 +1100 (EST), Damian Conway wrote:
But it makes "short-circuit as soon as Cgrep
lets through a specific value" ugly:
my $seen;
$has_odd_elem = grep { $seen last; $_%2 ++$seen }
I would propose that the Cgrep operation should short-circuit if the
block throws an exception, with the value of the expection determining
whether the final invocation of the block should accept the element it
was filtering:
Otherwise nice but until now die() has been a serious thing, now
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
Cmap 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
On Thu, Sep 07, 2000 at 06:28:25AM +1100, Damian Conway wrote:
I should have an RFC out on this by next week.
Feel free to hijack and/or infiltrate my RFC.
Damian
--
$jhi++; # http://www.iki.fi/jhi/
# There is this special biologist word we use for 'stable'.
# It is 'dead'.
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 ($_ = 2) ? 1 : 0 } (1,
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 unitialized
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 of those. But
On Thu, Sep 14, 2000 at 11:46:31AM -0400, 'John Porter' wrote:
Jarkko Hietaniemi wrote:
In the other camp, Cyield has been suggested; but
the conflation of that with its thread-related semantics may not
be a such good idea.
Cpass.
Well, "pass" might be o.k.; but it usu
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 think you
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 to the existing q{...}
is a good idea. If I had
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 the rest of
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
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
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 arrays,
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 having to
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 typing I could mark a scalar
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
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 in
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:
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 system
(Inferno) is available
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 your thoughts about Limbo? I did some Limbo
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 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 such
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; # magically uses
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 changing numbers to
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 ultratuned
quicksort (since
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 expand
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 document better)
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++; #
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, $^O
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 be there, what
kind
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 rest is just a matter of extending File::Spec
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 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 makes
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 turn the use
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 I have
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 of
the standard, the name
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
of them is very descriptive
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" -- I
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 namespaces.
Well, I didn't say *package
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 agree that
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 could
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 breaking requirements?
There isn't
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 those of you who didn't get the reference
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 ever saw it with his name on it.
I believe the first part
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?
I believe
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
bzip2 version
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 individual files inside
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.
Careful
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: both
pure Perl libraries
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 need
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.
1 - 100 of 139 matches
Mail list logo
