Re: Beefier prototypes (was Re: Multiple for loop variables)

At 03:24 PM 8/29/00 -0400, John Porter wrote: >Peter Scott wrote: > > > > Yes, please. I view the flattening of lists as a feature, not a bug, and > > it has made Perl a lot easier to understand IMHO. > >So... is an RFC forthcoming? Or shall I? I mailed an RFC on mul

Re: Structured exception handling should be a core module.

perl.org/msg03111.html that we could do better than checking integers: >I think I agree with the folks that say errors should be caught by >type, not by number. Just as a for instance, you ought to able to >write a simple handler that catches any ERRNO-style error. or whether I misunderstand. -- Peter Scott Pacific Systems Design Technologies

Re: RFC 52 (v2) List context return from filesystem functions

in the successful case being an empty list, though. And conversely. Maybe this isn't itching enough to be worth scratching this hard, but it seemed like a good direction :-( Anyone got any brilliant ideas before I withdraw it? -- Peter Scott Pacific Systems Design Technologies

Re: RFC 52 (v2) List context return from filesystem functions

At 07:39 PM 8/29/00 -0700, Dirk Myers wrote: >Tonight, the role of "Peter Scott" will be read by Perl RFC Librarian : > > > =head1 DESCRIPTION > > > > In a scalar context, the result should remain the same as it is now. It is > > very tempting to make the

Re: Multiple for loop variables

At 12:43 PM 8/29/00 -0400, Steve Simmons wrote: >On Mon, Aug 28, 2000 at 04:10:01PM -0400, Eric Roode wrote: > > Peter Scott wrote: > > >Graham Barr once allowed as how he thought it would be neat if you > could say > > > > > > for my($x, $y, $z) (@lis

Re: Do we really need eq?

At 12:57 PM 8/29/00 -0500, David L. Nicol wrote: >I'd like to see every number bundled with a "precision" attribute. It's >a holdover from when I was heavily into chemistry. Some of the other RFCs on the list also appear to have been triggered the same way. Oh, wa

Re: The distinction between "do BLOCK while COND" and "EXPR while COND" should go

are; but it's quite intuitive nonetheless. Get rid of some of the other weird uses of 'do', yes... -- Peter Scott Pacific Systems Design Technologies

Re: The distinction between "do BLOCK while COND" and "EXPR while COND" should go

At 02:30 PM 8/31/00 -0500, Christopher J. Madsen wrote: >Peter Scott writes: > > I dunno, maybe a last in a do block whose value is used by > > something should be a syntax error. We're talking about code like > > > > $x += do { $y = get_num; last if

Re: RFC 52 (v2) List context return from filesystem functions

hash context. :-( We will :-) RFC 21: >=item 'HASH' > >The subroutine was called in a context where its return value is >assigned to (or treated as???) a hash: > > %hash = func(); > @keys = keys func();# ??? -- Peter Scott Pacific Systems Design Technologies

Re: The distinction between "do BLOCK while COND" and "EXPR while COND" should go

hing obviously not a label. I dunno, maybe a last in a do block whose value is used by something should be a syntax error. We're talking about code like $x += do { $y = get_num; last if $y == 99; $y } while defined $y; right? *Shudder* -- Peter Scott Pacific Systems Design Technologies

Re: Proposal: chop() dropped

homp($line) to do chomping specific to a particular filehandle. Make sense? -- Peter Scott Pacific Systems Design Technologies

Re: RFC 175 (v1) Add C keyword to force list context (like C)

rays in a scalar context evaluate to their number of entries 3. Array slices evaluate to the list of their members Each one is reasonable, but boy, put them together and you can trip up even the wiley Antipodean Perl master (albeit in a chronically challenged state... so to speak). This is the kind of thing that keeps Perl instructors in business... -- Peter Scott Pacific Systems Design Technologies

Re: RFC 33 (v2) Eliminate bareword filehandles.

just pretend, even though >it's not quite true, that * is the type symbol for a filehandle >at least when it comes to passing it or storing in somewhere. >This works out quite well. This is true; but won't it make even more sense, and less pretense, just to pass filehandles around in scalars? -- Peter Scott Pacific Systems Design Technologies

Re: Globs, (brrr) scalar filehandles, prototypes.

laration syntax ought to change if there are no bareword filehandles? -- Peter Scott Pacific Systems Design Technologies

Re: RFC 173 (v1) Allow multiple loop variables in foreach statements

it alleviates some of the parsing >difficulty, since you still have a scalar expression between the >C and the C<(@list)>. Sorry, I missed/forgot that posting. I'll add it in. -- Peter Scott Pacific Systems Design Technologies

Re: RFC 177 (v1) A Natural Syntax Extension For Chained References

which is only one character longer than the proposal... -- Peter Scott Pacific Systems Design Technologies

Re: RFC 184 (v1) Perl should support an interactive mode.

want. Does what you want need to be in the core? -- Peter Scott Pacific Systems Design Technologies

Re: Change "($one, $two)=" behavior for optimization? (was Re: RFC 175 (v1) Add C keyword to force list context (like C))

#x27;s RFC'ing it. I like it too. Anyone working on the RFC? I wonder how the p526 translator will handle this. Suppose someone deliberately did ($line) = ; # Save next line, discard rest Maybe something like { ($line, my @plugh) = ; } -- Peter Scott Pacific Systems Design Technologies

Re: Change "($one, $two)=" behavior for optimization? (was Re: RFC 175 (v1) Add C keyword to force list context (like C))

At 10:52 AM 9/4/00 -0600, Nathan Torkington wrote: >Peter Scott writes: > > >> ($a, $b, $c) = ; > > >> or > > >> @a[4,1,5] = ; > > >> only read three lines? > > > > > >I think this is a superb idea, an

Re: The distinction between "do BLOCK while COND" and "EXPR while COND" should go

7) } tie $x, 'MaiTai'; $x = fn; $ /tmp/foo STORE: 7 Why don't I see three STOREs? >and you're left with 7. -- Peter Scott Pacific Systems Design Technologies

Re: Change "($one, $two)=" behavior for optimization? (was Re: RFC 175 (v1) Add C keyword to force list context (like C))

e, not the last, or they're in trouble: $ perl -e 'my($line)=<>;print $line' foo bar baz ^D foo -- Peter Scott Pacific Systems Design Technologies

Re: The distinction between "do BLOCK while COND" and "EXPR while COND" should go

f my($x,$y) = ($z,fn($w)). 'Expert' users were those who got more than 7 right. Unfortunately this is an empty gripe since I have no idea where to start simplifying. -- Peter Scott Pacific Systems Design Technologies

Re: The distinction between "do BLOCK while COND" and "EXPR while COND" should go

At 01:20 PM 9/3/00 +1100, Damian Conway wrote: >> Modulo some superpositional silliness, > >Hey! I resemble that remark! > >Damian I guess this means we should expect a N'Yuk module some time in the future... -- Peter Scott Pacific Systems Design Technologies

Re: RFC 39 (v3) Perl should have a print operator

Have we finally found a way to put println in Perl? (Ducks) > I am considering this as a possible addition to RFC 51: > > = $data; # print to tty and file I am not so crazy about this part though. -- Peter Scott Pacific Systems Design Technologies

Re: new -language sublists. perl6-language-datetime and perl6-language-errors

g RFCs into a more > cohesive whole. >DEADLINE: 2 weeks (August 29th) How is this different from perl6-language-flow? -- Peter Scott Pacific Systems Design Technologies

Re: RFC 33 (v2) Eliminate bareword filehandles.

:42:38 GMT ETag: "1251b5-2608-39a3563e" Accept-Ranges: bytes Content-Length: 9736 Connection: close Content-Type: text/plain I think it's time for a thread subject change. -- Peter Scott Pacific Systems Design Technologies

Re: RFC 151 (v2) Merge C<$!>, C<$^E>, C<$@> and C<$?>

Yes, that was in there before and was a casualty of bad editing. Thanks for catching it. >Finally, I'd vote for $! 1000 times over $@; I've always hated $@ >because of its direct conflict with sh's $@, which is a completely >different beast altogether. Ditto. -- Peter Scott Pacific Systems Design Technologies

Re: RFC 67 (v1) Deep Copying, aka, cloning around.

I like it. Can you tell me what semantics you use with something like this to get behavior like clone's, where the reult of a node depends on the results of other nodes? Whether they've been visited already or not, how do you parcel all the results of, say, a ref-to-array together? -- Peter Scott Pacific Systems Design Technologies

Re: RFC 151 (v1) Merge C<$!>, C<$^E>, and C<$@>

At 01:32 AM 8/25/00 +0200, Bart Lateur wrote: >On Thu, 24 Aug 2000 13:50:56 -0700, Peter Scott wrote: > >Yes, this is losing information; the former $! is no longer around. I > >contend that it's eliding functionality that is seldom, if ever, used, in > >favor o

Re: Pre-RFC: undef =~ s/def/initialize/

#x27;d vote for it. Makes a heck of a lot of sense. >You think of teasing. And I am. But if you think about it, this notion has >a lot going for it, too. -- Peter Scott Pacific Systems Design Technologies

Re: auto-initializing values

not something I've ever wanted. Have you? -- Peter Scott Pacific Systems Design Technologies

Re: $a in @b

outer enclosing labelled loop, otherwise I'd just propose overloading the one argument and say that if it's a reference, take the thing it refers to as the value and exit/continue the nearest enclosing loop. -- Peter Scott Pacific Systems Design Technologies

Re: Conversion of undef() to string user overridable for easy debugging

arch for this sentinel string. > >I must admit that apart from easy debugging, this feature would hardly >serve any other practical purpose. -- Peter Scott Pacific Systems Design Technologies

Re: RFC 52 (v2) List context return from filesystem functions

ways return true in a list context. This is only slightly better than returning false iff the function failed. > > > >>>>> "PS" == Peter Scott <[EMAIL PROTECTED]> writes: > >PS> At 06:40 AM 8/30/00 -0600, Tom Christiansen wrote: > >> >>My w

Re: Drop here docs altogether? (was Re: RFC 111 (v3) Here Docs Terminators (Was Whitespace and Here Docs))

lly much rather see a new qh// "quoted here doc" >operator that solves these problems than trying to jam them all into the >existing shell-like syntax, which is a leftover oddity, really. -- Peter Scott Pacific Systems Design Technologies

Re: RFC 216 (v1) POD should tolerate white space.

ed; it's RFC 93, "Regex: Support for incremental pattern matching". It has everything in there, it just might benefit from explicitly saying, "This is how people who want $/ to be a regex can get what they want" even though it may not be called $/ in Perl 6. -- Peter Scott Pacific Systems Design Technologies

Re: RFC 216 (v1) POD should tolerate white space.

y be considered independently. *Applause* There is no RFC on it unless it is hopelessly mistitled. This is something I've wanted for a long time. Someone working on the RFC? -- Peter Scott Pacific Systems Design Technologies

Re: RFC 16 (v2) Keep default Perl free of constraints such as warnings and strict.

e as possible, Those of us who prefer door #2 are still out here. By way of support, I adduce perl.pod: =head1 BUGS The B<-w> switch is not mandatory. -- Peter Scott Pacific Systems Design Technologies

Re: A common event loop

ll win. > >So the question I put to you all is, would it make sense for Perl to >have a common event loop from which all other modules can then draw, >thus avoiding the current state of conflict? Absolutely. The architecture of Tk applications will change considerably, for the better. -

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

WHERE foo IN (NULL)". You'd think that would be the same as "WHERE foo IS NULL", but n, we're talking about SQL here. (At least the Oracle brand of it.) Let's not venture one inch down that path. -- Peter Scott Pacific Systems Design Technologies

Re: $a in @b

e another? That's what my idea was, to provide a second argument. Also, shouldn't be necessary to label a loop if you don't have another one inside it, although if you did, it would avoid the embarrassment of "last undef, 'foo'" that fell out of my suggestion. -- Peter Scott Pacific Systems Design Technologies

Re: $a in @b

next does not include any return value, so what should it be? Of course, if it's false, you didn't need a next in the first place and if it's true you didn't need a grep in the first place :-) -- Peter Scott Pacific Systems Design Technologies

Re: $a in @b

ing than a new keyword. $0.02. -- Peter Scott Pacific Systems Design Technologies

Re: RFC 241 (v1) Pseudo-hashes must die!

quats => 42); would be allowed. So can we keep the option for fixed keys somehow? -- Peter Scott Pacific Systems Design Technologies

Re: RFC 241 (v1) Pseudo-hashes must die!

At 06:49 PM 9/17/00 -0400, Michael G Schwern wrote: >On Sun, Sep 17, 2000 at 03:37:07PM -0700, Peter Scott wrote: > > However, while we've got ways in P6 to do objects better without > > pseudo-hashes, a major benefit of them to me is nothing to do with > objects, > &

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

late undef to IS NULL when constructing queries, and DBI handily turns NULLs into undefs in results for me. If this is not about DBMS interfacing but you want Perl to implement SQL expression semantics, why? What possible benefit is there? -- Peter Scott Pacific Systems Design Technologies

Re: RFC 241 (v1) Pseudo-hashes must die!

ould use objects instead, but that's hardly the point.) I have been unable to come up with a lightweight syntax for saying that the second-level hash keys should be fixed. I supplicate the gods of new syntax for any succor they may render in my hour of need. -- Peter Scott Pacific Systems Design Technologies

Re: RFC 76 (v2) Builtin: reduce

g the NUL character, although of course an empty string actually is terminated by the NUL character, but you don't put it in..." -- Peter Scott Pacific Systems Design Technologies

Re: Variable attributes (was Re: RFC 355 (v1) Leave $[ alone.)

ent from the type of thing it contains. But what syntax will you use? If I make one up for the sake of illustration: my DogPound(Dog) @kennel :homeless; then @kennel->municipality, but $kennel[37]->breed. Make sense, or should I just go back to bed? -- Peter Scott Pacific Systems Design Technologies

Re: pack/unpack is damn unperlish. Explain them as Perl.

don't think there's anything wrong with the interface though, it seems quite appropriate. -- Peter Scott Pacific Systems Design Technologies

Re: Generalizing ?? !!

ey be made so? pugs> my $a = 42; (1 && $a) = 17; *** Can't modify constant item: VInt 42 pugs> my $b = 42; ($b || 0) = 17; *** Can't modify constant item: VInt 42 -- Peter Scott

Re: Generalizing ?? !!

On Fri, 22 Jun 2007 15:40:37 +0100, Aaron Crane wrote: > Peter Scott writes: >> can someone tell me why you can't just use && ... || in place of ?? >> ... !!, now that && and || propagate context to both sides? > > You get the wrong result when the antece

Re: Web Module (Was: Perl6 new features)

tinue the tradition of tending to err on the side of "practical" over "elegant". It may not seem rational that avoiding the need to type "cpan Foo::Bar" makes a huge difference, but I believe it does, for certain modules. -- Peter Scott http://www.perlmedic.com/ http://www.perldebugged.com/

Re: Web Module (Was: Perl6 new features)

6 for OS and embedded systems integrators -- Peter Scott http://www.perlmedic.com/ http://www.perldebugged.com/

Re: Standards bearers (was "Re: xml and perl 6")

value judgments and we don't like to make those and people will argue about their decisions no matter what, but does that have to stop us? [1] http://groups.google.com/group/perl.perl5.porters/msg/74ecce32ff1ad845?dmode=source -- Peter Scott http://www.perlmedic.com/ http://www.perldebugged.com/

RE: Allowing '-' in identifiers: what's the motivation?

ho give up on reading the other people's programs. I'm all for giving people enough rope to either hang themselves or make a hammock, but do we really want to open this can of worms? -- Peter Scott http://www.perlmedic.com/ http://www.perldebugged.com/

Re: Allowing '-' in identifiers: what's the motivation?

ion in reading code. Even if subconsciously, even if measured in milliseconds, I contend that is important. Just because some other languages do it doesn't mean Perl should, unless you know of some studies showing that readability hasn't been impaired. I'm willing to be surprised. -- Peter Scott http://www.perlmedic.com/ http://www.perldebugged.com/

Re: RFD: Built-in testing

Clintonesque parsing when it encounters the token. Okay. But how do I justify the new syntax to a student? What are they getting that makes up for what looks like a fall in readability? -- Peter Scott http://www.perlmedic.com/ http://www.perldebugged.com/

Re: underscores vs hyphens (was Re: A new era for Temporal)

eld in the Unicode tables, right?) Also, what happens when code gets run through mailers or other programs that think a hyphen is an acceptable place to break a line? Does the code still work after copy and paste with that newline inserted? -- Peter Scott http://www.perlmedic.com/ http://w

Re: ding!

On 5/31/17 8:44 PM, ToddAndMargo wrote: On 05/31/2017 08:39 PM, Lloyd Fournier wrote: perl6 -e 'say "\a"' No joy under linux. 0x07 does not work either. Just prints a 7 ITYM chr(7).

Missing or wrong version of dependency

Hullo.  I am on     CentOS Linux release 7.5.1804 (Core) and I did     yum install rakudo    [rakudo-0.2018.04-1.el7]     yum install rakudo-zef  [rakudo-zef-0.2.9-1.el7.x86_64] Both came from epel.  Then I tried this: # zef install Readline ===SORRY!=== Missing or wrong version of depend

Re: RFE: contains documentation

this right (at least, initially) by creating the ---tut series of pods. Good programmers are not always good writers or teachers. Peter Scott Author, "Perl Debugged," "Perl Medic," and "Perl Fundamentals."

Re: RFE: contains documentation

On 9/9/18 3:47 PM, ToddAndMargo wrote: I also LOVE examples.  Sometimes an example will get past the fog quicker than anything else.  And you will notice in a (spoken) language dictionary, they ALWAYS give an example of how to use a work in its various contexts. "Learning Perl 6" by brian d fo

Re: A comparison between P5 docs and p6 docs

Ordinarily I would agree with you. But I know my own brain and how it works. I only learn by doing. Have tried to change that and can't. A good tutorial book *will* make you "do." The brian d foy book does exactly that with things to try, and questions to explore in your own code. It takes

Re: Could this be any more obscure?

On 9/26/2018 3:21 PM, ToddAndMargo wrote: I use words all the time.  I never would have figured it out from     multi method words(Str:D $input: $limit = Inf --> Positional) Do your really think any beginner would be able to figure out "words" from the above? If the beginner had studied the

Re: Could this be any more obscure?

On 9/30/18 2:45 AM, ToddAndMargo wrote: The manual need to be written for the common user to understand, not just developer level and very advanced users.  They don't need the manual anyway. Of course we do. I constantly refer to the Perl 5 manual rather than waste memory on rote information.

Re: Could this be any more obscure?

On 10/2/2018 5:45 PM, ToddAndMargo wrote: On 10/2/18 5:31 PM, Curt Tilmes wrote: On Tue, Oct 2, 2018 at 8:28 PM ToddAndMargo > wrote:     Question: in Perl syntaxland, is "postfix" short     for "postcircumfix"? Nope.  Each are different types of oeprator.  Her

Re: need doc help with []

On 10/2/2018 6:29 PM, Trey Harris wrote: So it is for the [] postcircumfix. For those of us who have been following Perl 6 development for 18 years, the fact that it—and almost every other low-level particle—can be described at all in such a way is a remarkable triumph of the language. Amen t

Re: [perl6/specs] 58fe2d: [S12] spec setting and getting values of attribute...

iolated the separation of thingummy (my terminology isn't so good here, I trust you know what I mean). I don't know how you solve this but please think about this use case. Of course not every object can or should be serialized but elective object persistence is pretty important.

Re: The trouble with awesome

rest were sysadmins). Now the landscape looks very different. -- Peter Scott

Re: Perl 6 Advocacy Suggestion

I have seen Damian demonstrate how Perl 6 can be the best language for teaching functional, procedural, and object-oriented programming. On 1/19/2016 10:37 AM, Darren Duncan wrote: I very much agree with this idea, of arguing Perl 6 as a teaching language. Academia are the ones that would appre

Re: I am getting flooded with tmp files

Something in your program is keeping them open until your program closes the filehandles on exit.  Unlink can't remove a file that's open, only make a note for later. Restricting the scope of the temp file handles would probably be the cleanest way. On 11/18/2024 8:49 PM, ToddAndMargo via per

<    1   2   3