At 11:36 PM 2/11/2001 -0500, Sam Tregar wrote:
>On Sun, 11 Feb 2001, Jan Dubois wrote:
>
> > However, I couldn't solve the problem of "deterministic destruction
> > behavior": Currently Perl will call DESTROY on any object as soon as the
> > last reference to it goes out of scope. This becomes im
On Sun, 11 Feb 2001 22:30:30 -0500, "Bryan C. Warnock"
<[EMAIL PROTECTED]> wrote:
>crossed to -internals
Ok, I removed -language.
>Jan Dubois:
>> Not necessarily; you would have to implement it that way: When you try to
>> open a file and you don't succeed, you run the garbage collector and try
On Sun, 11 Feb 2001, Jan Dubois wrote:
> However, I couldn't solve the problem of "deterministic destruction
> behavior": Currently Perl will call DESTROY on any object as soon as the
> last reference to it goes out of scope. This becomes important if the
> object own scarce external resources (
On Sun, Feb 11, 2001 at 08:18:30PM -0700, Nathan Torkington wrote:
> Just speaking for myself, I'd rather see an apology. A retraction
> is impersonal, but an apology implies you regret it.
Fair enough. I saw a retraction as "eek, I didn't mean to say *that*".
Sorry, brian. I *didn't* mean to sa
Simon Cozens writes:
> I did say that I retracted my remarks.
Just speaking for myself, I'd rather see an apology. A retraction
is impersonal, but an apology implies you regret it.
If I appear to be hounding you about it, it's because I'm appalled. I
expect sensitivity and courtesy from everyo
crossed to -internals
Jan Dubois:
> Not necessarily; you would have to implement it that way: When you try to
> open a file and you don't succeed, you run the garbage collector and try
> again. But what happens in the case of XS code: some external library
> tries to open a file and gets a failu
On Sun, 11 Feb 2001 21:11:09 -0500, "Bryan C. Warnock"
<[EMAIL PROTECTED]> wrote:
>On Sunday 11 February 2001 19:08, Jan Dubois wrote:
>> However, I couldn't solve the problem of "deterministic destruction
>> behavior": Currently Perl will call DESTROY on any object as soon as the
>> last referen
On Sun, Feb 11, 2001 at 06:40:49PM -0700, Nathan Torkington wrote:
> Apologizing would be a good place to start. As many folks have
> pointed out, it's hard to find capable intelligent volunteers.
> And you just chased one away, a reprehensible act of destruction.
I did say that I retracted my r
On Sunday 11 February 2001 19:08, Jan Dubois wrote:
> However, I couldn't solve the problem of "deterministic destruction
> behavior": Currently Perl will call DESTROY on any object as soon as the
> last reference to it goes out of scope. This becomes important if the
> object own scarce external
On Fri, 09 Feb 2001 13:19:36 -0500, Dan Sugalski <[EMAIL PROTECTED]> wrote:
>Almost all refcounting schemes are messy. That's one of its problems. A
>mark and sweep GC system tends to be less prone to leaks because of program
>bugs, and when it *does* leak, the leaks tend to be large. Plus the
Simon Cozens writes:
> > okay. i quit.
>
> Well, hm. I'd rather we actually made something positive out of this.
Apologizing would be a good place to start. As many folks have
pointed out, it's hard to find capable intelligent volunteers.
And you just chased one away, a reprehensible act of de
By the way, Ed, mail to you is bouncing with user unknown.
--
$\=" ";@a=qw/hacker, Perl another Just/;sub TIESCALAR{bless[]};tie $a,$a;
*STORE=*FETCH=sub{print pop @a};$_++for$a,$a;
On Sun, Feb 11, 2001 at 03:30:19PM -0800, Edward Peschko wrote:
> And PR is a function of people listening to people that they know (and
> presumably respect). As much as we make summaries, et al, it is Larry that
> they primarily know. And Larry saying something will get it put on slashdot.
Ye
[Please be careful with attributions -- I didn't write any
of the quoted material...]
Russ Allbery wrote:
> >> sub test {
> >> my($foo, $bar, %baz);
> >> ...
> >> return \%baz;
> >> }
> That's a pretty fundamental aspect of the Perl language; I use that sort
Bart Lateur wrote:
> On Fri, 09 Feb 2001 12:06:12 -0500, Ken Fox wrote:
> > 1. Cheap allocations. Most fast collectors have a one or two
> >instruction malloc. In C it looks like this:
> >
> > void *malloc(size) { void *obj = heap; heap += size; return obj; }
> > ...
>
> That is not a ga
On Sun, Feb 11, 2001 at 05:03:12PM +, Simon Cozens wrote:
> There's obvious FUD out there and we don't seem to be giving the impression of
> getting much done, or doing anything to counter it.
Let's be fair. We're not getting much done, and that's a *GOOD* thing.
Language design is a very
On Sun, Feb 11, 2001 at 11:05:22PM +, Simon Cozens wrote:
> On Sun, Feb 11, 2001 at 03:00:05PM -0800, Edward Peschko wrote:
> > Again, We'll have continued discussion, but what the perl development
> > project needs right now is a swift kick of *direction* from larry. And I'm
> > pretty sure t
On Sun, Feb 11, 2001 at 03:00:05PM -0800, Edward Peschko wrote:
> Again, We'll have continued discussion, but what the perl development
> project needs right now is a swift kick of *direction* from larry. And I'm
> pretty sure that he knows this.
I thought part of the idea was that we become self
On Sun, Feb 11, 2001 at 05:03:12PM +, Simon Cozens wrote:
> On Sun, Feb 11, 2001 at 11:28:45AM -0500, brian d foy wrote:
> > okay. i quit.
>
> Well, hm. I'd rather we actually made something positive out of this.
>
> There's obvious FUD out there and we don't seem to be giving the impressio
ight, and grant
you a non-exclusive right to publish. The HTML edition will be placed
at
http://www.simon-cozens.org/perl6/THISWEEK-MMDD.html
That is, this week's will be at
http://www.simon-cozens.org/perl6/THISWEEK-20010211.html
Please let me know what you're going to d
On Mon, Feb 05, 2001 at 03:35:18PM -0200, Branden wrote:
> It [aliasing] means that the behaviour of $a/@a/%a is felt on $b/@b/%b, and
> vice-versa, so that they are both the same thing. In vtable terms, the
> vtable of $b/@b/%b would get copied to $a/@a/%a
No, no, not at all. Aliasing is a feat
You should probably also take a look a Debian's packaging, the .deb.
It consists of an ar archive containing three files: one for the magic
(named debian-binary, containing "2.0"), one for the filesystem image
(filesystem.tar.gz)
On Fri, Feb 09, 2001 at 06:17:34PM -0200, Branden wrote:
> | Pla
On Sun, Feb 11, 2001 at 05:03:12PM +, Simon Cozens wrote:
> In order to do something about this, I suggest that we should:
> i) ...
> ii) ...
I forgot iii)...
Ask, could we have the PDDs placed up on dev.perl.org in the same way as the
RFCs, please?
So far we have
http:[EMAIL PROTECTED]/ms
On Sun, Feb 11, 2001 at 11:28:45AM -0500, brian d foy wrote:
> okay. i quit.
Well, hm. I'd rather we actually made something positive out of this.
There's obvious FUD out there and we don't seem to be giving the impression of
getting much done, or doing anything to counter it. Part of the probl
On Sun, 11 Feb 2001, Simon Cozens wrote:
> Hey, Brian, you're meant to be the PR guy.
>
> Your strategy might work in the corporate world, but in the open source
> world, the first rule of PR is to actually make sense. This may come as
> a bit of a shock, I know.
> Please sort it out. Now.
okay
On Sun, Feb 11, 2001 at 06:57:03AM +, Simon Cozens wrote:
> Likewise. More so since I didn't even receive it.
I retract that; I've been having mail problems all weekend and it's
since arrived.
> Brian, you're not in my good books today, this month or this year.
> Please sort it out. Now.
I
On Fri, 9 Feb 2001 16:14:34 -0800, Mark Koopman wrote:
>but is this an example of the way people SHOULD code, or simply are ABLE to
>code this. are we considering to deprecate this type of bad style, and force
>to a programmer to, in this case, supply a ref to %baz in the arguements to
>this s
27 matches
Mail list logo
