Re: RFC 109 (v1) Less line noise - let's get rid of @%

2000-08-17 Thread Damien Neil
On Thu, Aug 17, 2000 at 03:10:44PM -0700, Steve Fink wrote: > My proposal would be what I implemented for perl5 a while back (Sarathy > didn't dislike it, but wasn't convinced enough to put it in): all > dereferencing can be done with ->. > > $x->@ is the same as @$x > $x->% is the same as %$x >

Re: RFC 109 (v1) Less line noise - let's get rid of @%

2000-08-16 Thread Damien Neil
On Wed, Aug 16, 2000 at 10:24:09AM -0400, Karl Glazebrook wrote: > It was the response which was blithe, it just re-iterated arguments we > are all completely familar with and did not address my point in the RFC. Then perhaps we need to agree to disagree. I feel that a number of people have addr

Re: RFC 109 (v1) Less line noise - let's get rid of @%

2000-08-16 Thread Damien Neil
On Wed, Aug 16, 2000 at 12:31:23PM -0400, John Porter wrote: > Sorry, this is exactly the argument we get from the C/C++/Java heads, > who find perl's lack of discrimination between strings and numbers so > distasteful. But if we can gloss over the difference between a string > and a number, we c

Re: $!

2000-08-17 Thread Damien Neil
On Thu, Aug 17, 2000 at 01:19:22PM -0500, Jarkko Hietaniemi wrote: > I recently suggested in p5p that for many system calls it could be > checked in *consta...darn, *compile* time whether they are used in > void contect, and _abort_. "No, I'm not going to let you get away > with doing a chdir() a

Re: why not just use C /* ... */ ?

2000-08-23 Thread Damien Neil
On Thu, Aug 24, 2000 at 08:41:46AM +1000, iain truskett wrote: > Does it try to parse other escape sequences (such as \t, \n, \r etc.) or > just the Unicode one? No, just the Unicode escapes. Think of it as trigraphs in C -- it's there so you can translate code from a more-featureful character s

Re: why not just use C /* ... */ ?

2000-08-23 Thread Damien Neil
On Thu, Aug 24, 2000 at 06:53:31AM +1000, iain truskett wrote: > >/* File: C:\user\jv\demo.java */ > > > t.java:1: Invalid escape character. > > /* File: C:\user\jv\demo.java */ > > In that situation, I would say that the java compiler isn't really doing > what it should be doing. i.e. That

Re: RFC 110 (v3) counting matches

2000-08-28 Thread Damien Neil
On Mon, Aug 28, 2000 at 06:05:03PM -0400, Mark-Jason Dominus wrote: > # WRONG > while (($mo, $dy, $yr) = ($string =~ /\d\d-\d\d-\d\d/g)) { > ... > } I assume you mean: while (($mo, $dy, $yr) = ($string =~ /(\d\d)-(\d\d)-(\d\d)/g)) { ... } Drawing on some

Re: RFC 110 (v3) counting matches

2000-08-28 Thread Damien Neil
On Mon, Aug 28, 2000 at 01:30:41PM -0500, Jarkko Hietaniemi wrote: > > $count = () = $string =~ /pattern/g; > > Which I find cute as a demonstration of the Perl's context concept, > but ugly as hell from usability viewpoint. I how to assign to an > empty list to get a number of something? H

Re: RFC 109 (v1) Less line noise - let's get rid of @%

2000-08-15 Thread Damien Neil
On Tue, Aug 15, 2000 at 05:45:04PM -0400, Karl Glazebrook wrote: > I hope people will actually read the RFC before coming back with these > canned responses which I (and presumably everyone else on this list) > am completely familiar with. I used to believe that too! Honest... I think you do a si

Re: RFC 76 (v2) Builtin: reduce

2000-09-19 Thread Damien Neil
On Tue, Sep 19, 2000 at 08:14:24PM -0600, Tom Christiansen wrote: > >Following Glenn's lead, I'm in the process of RFC'ing a new null() > >keyword and value > > As though one were not already drowning in a surfeit of subtly > dissimilar false values. Hear, hear. Three-valued logic is enough.

Re: RFC 263 (v1) Add null() keyword and fundamental data type

2000-09-20 Thread Damien Neil
On Wed, Sep 20, 2000 at 11:58:08AM -0700, Glenn Linderman wrote: > > I think that this is better done as a special overloaded object used > > by database modules which wish to implement SQL-style tri-state logic. > > It could be done as an overloaded object. You'd have to be able to overload all

Re: RFC 263 (v1) Add null() keyword and fundamental data type

2000-09-20 Thread Damien Neil
On Wed, Sep 20, 2000 at 01:21:52PM -0700, Russ Allbery wrote: > No offense to Damian, but I tried to read and understand his documentation > and I thought I was back in grad school. I don't think it's the fault of > the writing either; I think that Quantum::Superpositions is trying to do > someth

Re: RFC 263 (v1) Add null() keyword and fundamental data type

2000-09-20 Thread Damien Neil
On Wed, Sep 20, 2000 at 02:47:01PM -0600, Tom Christiansen wrote: > In Perl, this is the null character: "\0" ... > It's a shame you don't like it, but this is the way we speak. Well, it's the way you speak. Myself, I'd call that the NUL character. :> - Damien, exercising a pet pe

Re: $a in @b

2000-09-07 Thread Damien Neil
On Fri, Sep 08, 2000 at 09:45:54AM +1100, Damian Conway wrote: > I would propose that the C 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: I do

Re: RFC 357 (v1) Perl should use XML for documentation instead of POD

2000-10-02 Thread Damien Neil
On Mon, Oct 02, 2000 at 09:21:51AM -0700, Glenn Linderman wrote: > Indeed, this is the key problem with human use of XML. HTML was originally > simple enough to be human writable, its later, more powerful incarnations > start losing that (but you can always use a subset for simple things, and > X

Re: RFC 263 (v1) Add null() keyword and fundamental data type

2000-09-20 Thread Damien Neil
On Wed, Sep 20, 2000 at 04:12:09AM -, Perl6 RFC Librarian wrote: > Add null() keyword and fundamental data type I think that this is better done as a special overloaded object used by database modules which wish to implement SQL-style tri-state logic. Given that making overloaded objects fast

<    1   2