RFC 132: subroutines should be able to return an lvalue

2000-08-18 Thread Syloke Soong
func(args) = ... func(args) += ... func(args) =~ s/// Such functions have been modeled in object models that accept arg-list+operator (head+operator) polymorphic signatures. It would be up to the programmer of func() to dictate what happens when func() is invoked. The following

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

2000-08-17 Thread Syloke Soong
again. [EMAIL PROTECTED] on 08/17/2000 10:48:00 AM To: cc: [EMAIL PROTECTED]@Internet (bcc: Syloke Soong/Americas/NSC) Subject:Re: RFC 109 (v1) Less line noise - let's get rid of @% To go through a few points that has arisen: o Why do I think "@" is useless? OK

RFC 58 (v1) Cchomp() changes.

2000-08-16 Thread Syloke Soong
chomp should have options to define what an EOL is. Many times, on Solaris, I could not use chomp because I had to use =~ s/[\n\r ]$// on files that came from NT or even from MS-oriented unix editors.

use strict

2000-08-15 Thread Syloke Soong
. On the other hand, my meat becomes some else's poison. Symmetry promotes expectancy. Expectancy is an expression of certainty, which is an attribute of quality. And quality, productivity. [EMAIL PROTECTED] on 08/14/2000 09:40:00 PM To: [EMAIL PROTECTED]@Internet cc: (bcc: Syloke Soong

Re: RFC 89 (v2) Controllable Data Typing

2000-08-14 Thread Syloke Soong
:00 PM To: Syloke Soong/Americas/NSC@NSC cc: [EMAIL PROTECTED]@Internet Subject:Re: RFC 89 (v2) Controllable Data Typing I don't think this RFC is the place to try and cover all of the 'constraints' that might be in perl 6. Sure, this RFC may as well be the one to formalise