Re: Short term Zef fix

0/04/2019 12:06, Simon Proctor wrote: >> >> Until the p6c system is fixed here's a short term fix that will at least >> let zef install modules from cpan. >> >> zef --help >> This lists a config file mine is : >> >> CONFIGURATION /home/sproctor/.config/zef

Re: Short term Zef fix

Browsing zef's options I see that a --/p6c may be used instead of editing the configuration file. JJ's caveat still valid though. On Tue, Apr 30, 2019 at 12:07 PM Simon Proctor wrote: > Until the p6c system is fixed here's a short term fix that will at least > let zef install modules fro

Re: Short term Zef fix

Not tried that On Tue, 30 Apr 2019 at 12:35, Timo Paulssen wrote: > Doesn't updating zef to the latest version fix everything up nicely? > - Timo > On 30/04/2019 12:06, Simon Proctor wrote: > > Until the p6c system is fixed here's a short term fix that will at least > let z

Re: Short term Zef fix

Doesn't updating zef to the latest version fix everything up nicely?   - Timo On 30/04/2019 12:06, Simon Proctor wrote: > Until the p6c system is fixed here's a short term fix that will at > least let zef install modules from cpan. > > zef --help > This lists a c

Re: Short term Zef fix

El mar., 30 abr. 2019 a las 13:03, Simon Proctor () escribió: > Oooh. How would I do that? > There's a phase-timeout option for zef, such as --fetch-timeout I'm not sure if that applies to repos, though... I seem to remember somebody mentioned, maybe in the IRC channel, another option, but can't

Re: Short term Zef fix

Oooh. How would I do that? (Like I say it's a short term fix as hopefully we'll get p6c back soonish). On Tue, 30 Apr 2019 at 12:01, JJ Merelo wrote: > The problem with that is that it will go from using the old version of the > file (and old versions of modules there) to none of them

Re: Short term Zef fix

The problem with that is that it will go from using the old version of the file (and old versions of modules there) to none of them. It's probably better to lower the timeout... El mar., 30 abr. 2019 a las 12:07, Simon Proctor () escribió: > Until the p6c system is fixed here's a short term

Short term Zef fix

Until the p6c system is fixed here's a short term fix that will at least let zef install modules from cpan. zef --help This lists a config file mine is : CONFIGURATION /home/sproctor/.config/zef/config.json Open that file and fine the "p6c" section. Set enabled to 0 and zef will s

[perl #128462] [PARSER] Unspace after a sigil-less term causes parser error

lly to only then accept a single space character there. > One wonders what nefarious corner case that covers. > > The real problem comes with that fourth alternative. We of > course need to support calling with no parens for argumentless > forms. But that case can fal

[perl #128462] [PARSER] Unspace after a sigil-less term causes parser error

be silly to only then accept a single space character there. One wonders what nefarious corner case that covers. The real problem comes with that fourth alternative. We of course need to support calling with no parens for argumentless forms. But that case can fall through to either of term:sym<na

Re: What is P6 for P5 `use Term::ReadKey`?

On 16/09/17 05:19, ToddAndMargo wrote: > On 09/13/2017 01:36 PM, Trey Harris wrote: >> L1 is an “ordinary method” (denoted, obviously enough, with the >> declarator |method|), which as described in the Typesystem >> doc, “defines >> objects of

Re: What is P6 for P5 `use Term::ReadKey`?

On 09/13/2017 01:36 PM, Trey Harris wrote: On Sat, Sep 9, 2017 at 3:55 PM ToddAndMargo toddandma...@zoho.com wrote: On 09/09/2017 07:00 AM, Timo Paulssen wrote: > This should be

Re: What is P6 for P5 `use Term::ReadKey`?

Thanks for that Trey! Previously I would just glance at those definitions and move straight to the examples. Now I can read them! Something like this explanation should be on a docs.perl6.org page. Maybe it is and I've just not found it. On 14 September 2017 at 06:36, Trey Harris

Re: What is P6 for P5 `use Term::ReadKey`?

On 09/13/2017 01:36 PM, Trey Harris wrote: On Sat, Sep 9, 2017 at 3:55 PM ToddAndMargo toddandma...@zoho.com wrote: On 09/09/2017 07:00 AM, Timo Paulssen wrote: > This should be enlightening: https://docs.perl6.org/routine/getc >

Re: What is P6 for P5 `use Term::ReadKey`?

On Sat, Sep 9, 2017 at 3:55 PM ToddAndMargo toddandma...@zoho.com wrote: On 09/09/2017 07:00 AM, Timo Paulssen wrote: > > This should be enlightening: https://docs.perl6.org/routine/getc > > > > Problem: also from the link: > > method getc(IO::Handle:D:

Re: What is P6 for P5 `use Term::ReadKey`?

On 09/08/2017 11:41 PM, ToddAndMargo wrote: Hi All! I am trying to convert some Perl 5 code to Perl 6. What do I use in place of use Term::ReadKey qw ( ReadKey ReadMode ); I am trying to convert the following: use Term::ReadKey qw ( ReadKey ReadMode ); sub DumpKeyboard () { # Dump

Re: What is P6 for P5 `use Term::ReadKey`?

On 09/09/2017 02:02 PM, Timo Paulssen wrote: The important part of the page is actually the one titled "Waiting for potential combiners". You'll want to either use binary encoding instead of utf8 (the default) or use an encoding that doesn't have combiners, like latin1 or ascii. Problem:

Re: What is P6 for P5 `use Term::ReadKey`?

The important part of the page is actually the one titled "Waiting for potential combiners". You'll want to either use binary encoding instead of utf8 (the default) or use an encoding that doesn't have combiners, like latin1 or ascii. > Problem: also from the link: > > method

Re: What is P6 for P5 `use Term::ReadKey`?

On 09/09/2017 07:00 AM, Timo Paulssen wrote: This should be enlightening: https://docs.perl6.org/routine/getc Hi Timo, From the link: Buffering terminals Using getc to get a single keypress from a terminal will only work properly if you've set the terminal to "unbuffered".

Re: What is P6 for P5 `use Term::ReadKey`?

On 09/09/2017 11:28 AM, Brandon Allbery wrote: On Sat, Sep 9, 2017 at 2:57 AM, ToddAndMargo <toddandma...@zoho.com <mailto:toddandma...@zoho.com>> wrote: This guy maybe? https://github.com/krunen/term-termios/blob/master/README.md <https://github.com/krunen/te

Re: What is P6 for P5 `use Term::ReadKey`?

On Sat, Sep 9, 2017 at 2:57 AM, ToddAndMargo <toddandma...@zoho.com> wrote: > This guy maybe? > > https://github.com/krunen/term-termios/blob/master/README.md > > I can't tell what he is saying. > > And his example wont read a carriage return That's very low level. A

Re: What is P6 for P5 `use Term::ReadKey`?

This should be enlightening: https://docs.perl6.org/routine/getc

Re: What is P6 for P5 `use Term::ReadKey`?

On 09/09/2017 12:07 AM, ToddAndMargo wrote: On 09/08/2017 11:41 PM, ToddAndMargo wrote: Hi All! I am trying to convert some Perl 5 code to Perl 6. What do I use in place of use Term::ReadKey qw ( ReadKey ReadMode ); I am trying to convert the following: use Term::ReadKey qw ( ReadKey

Re: What is P6 for P5 `use Term::ReadKey`?

On 09/08/2017 11:41 PM, ToddAndMargo wrote: Hi All! I am trying to convert some Perl 5 code to Perl 6. What do I use in place of use Term::ReadKey qw ( ReadKey ReadMode ); I am trying to convert the following: use Term::ReadKey qw ( ReadKey ReadMode ); sub DumpKeyboard () { # Dump

Re: What is P6 for P5 `use Term::ReadKey`?

On 09/08/2017 11:41 PM, ToddAndMargo wrote: Hi All! I am trying to convert some Perl 5 code to Perl 6. What do I use in place of use Term::ReadKey qw ( ReadKey ReadMode ); I am trying to convert the following: use Term::ReadKey qw ( ReadKey ReadMode ); sub DumpKeyboard () { # Dump

What is P6 for P5 `use Term::ReadKey`?

Hi All! I am trying to convert some Perl 5 code to Perl 6. What do I use in place of use Term::ReadKey qw ( ReadKey ReadMode ); I am trying to convert the following: use Term::ReadKey qw ( ReadKey ReadMode ); sub DumpKeyboard () { # Dump the contents of the keyboard buffer, if any

[perl #131754] [LTA] Error message when using a term bareword as if it were a subroutine

A possibly better way to phrase it: ===SORRY!=== Error while compiling [...] Constant "foo" is followed by another term at [...] --> say foo⏏ 4; If your meant to refer to the subroutine "foo" declared at [...], then either: * Use `fo

[perl #131754] [LTA] Error message when using a term bareword like a subroutine

e thrown when the user writes e.g. foo 42; as if `foo` were a subroutine, but it's actually some other kind of bareword such as: * a constant - `constant foo = ...` * a sigilless variable - `my \foo = ...` * a typename - `class foo { ... }` * a label - `foo:

[perl #128462] [BUG] Unspace after a sigil-less term causes parser error

This bug is still present in This is Rakudo version 2017.05-272-gfa7aa1c36 built on MoarVM version 2017.05-25-g62bc54e9 implementing Perl 6.c.

[perl #131389] Some parsing glitch with `\term` in a string

ses emoji cat in a string and it works; The second one tries to do the same in a bit more elaborate eval and it crashes with bogus term error; The third one executes the same code, except swapping \term:<> to \x, and it works fine; The fourth one executes the same code, except swapping \term:<

Re: [perl #128462] [BUG] Unspace after a sigil-less term causes parser error

cket/Display.html?id=128462 > > > >my \term = 42; > say term.Str;# Works fine >say term\ .Str; # Error: "Variable '' is not declared" FWIW, it looks like a problem in the Optimizer of all places: $ 6l 'my \a = 42; say a\ .Str' Variable '' is not dec

Re: [perl #128462] [BUG] Unspace after a sigil-less term causes parser error

cket/Display.html?id=128462 > > > >my \term = 42; > say term.Str;# Works fine >say term\ .Str; # Error: "Variable '' is not declared" Thanks for the report. Please note that you don’t need to unspace anymore in the given case: say term .Str just works since just before Christmas :-) Liz

[perl #128462] [BUG] Unspace after a sigil-less term causes parser error

# New Ticket Created by Sam S. # Please include the string: [perl #128462] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=128462 > my \term = 42; say term.Str;# Works fine say term\ .Str; # Error: "

[perl #126211] [PATCH] Use Terminal::ANSIColor instead of Term::ANSIColor

Patch was applied with commit cd8ce4e639. I'm closing this ticket as 'resolved'.

[perl #126211] [PATCH] Use Terminal::ANSIColor instead of Term::ANSIColor

# New Ticket Created by Shoichi Kaji # Please include the string: [perl #126211] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=126211 > As in https://github.com/tadzik/perl6-Term-ANSIColor/commit/be708da23d, Term::ANSICo

[perl6/specs] 8284cd: Correct spec of context aspects of the self term.

: M S12-objects.pod Log Message: --- Correct spec of context aspects of the self term. Commit: 1ca72032a6bb3dc0011637edd629819a2a9cfbd3 https://github.com/perl6/specs/commit/1ca72032a6bb3dc0011637edd629819a2a9cfbd3 Author: Will Coke Coleda w...@coleda.com Date: 2015-01

[perl6/specs] 8284cd: Correct spec of context aspects of the self term.

: M S12-objects.pod Log Message: --- Correct spec of context aspects of the self term.

[perl6/specs] de5fbb: [S32::Exception] Add X::Syntax::Term::MissingIniti...

: M S32-setting-library/Exception.pod Log Message: --- [S32::Exception] Add X::Syntax::Term::MissingInitializer

[perl #117695] It is possible to alias ... by using the term syntactic category -- broken

This now dies with Term definition requires an initializer: $ perl6-m -e 'my \term:a = 1;' ===SORRY!=== Error while compiling -e Term definition requires an initializer at -e:1 -- my \term⏏:a = 1; expecting any of: scoped declarator It works with STD: $ viv -c -e 'my \term:a = 1

[perl #119875] [BUG] term:^^ doesn't consider a last empty line as a line in regexes in Rakudo

# New Ticket Created by Carl Mäsak # Please include the string: [perl #119875] # in the subject line of all future correspondence about this issue. # URL: https://rt.perl.org:443/rt3/Ticket/Display.html?id=119875 masak rn: say abc\n ~~ /abc\n^^/ # why doesn't this match? camelia rakudo

[perl #119875] [BUG] term:^^ doesn't consider a last empty line as a line in regexes in Rakudo

S05:792 mentions this case explicitly: ^^ always matches the beginning of the string and after any \n that is not the final character in the string. So, rakudo is performing exactly as specced. I suspect the reason behind the spec is so that slurped \n-terminated files (i.e., the vast

[perl6/specs] 912d12: [S09] Add the term semilist to S09

: M S09-data.pod Log Message: --- [S09] Add the term semilist to S09 This way someone seeing the mention of semilist in S03 can search through the spec and find the place where it's discussed in detail, S09, just by searching for the term itself, rather than thinking to search

[perl #117695] It is possible to alias ... by using the term syntactic category -- broken

-routines.pod#L1282: It is possible to alias to a non-identifier by using the term syntactic category: my \term:∞ = Inf; Actual = Quoting http://irclog.perlgeek.de/perl6/2013-04-21#i_6730567: 18:38 raiph rn: my \term:a = 1 # golfed version of not-working-in-rakudo S06:1284 18:38

[perl6/specs] cac7e3: [S05] prefer term frugal to eager/minimal

paths: M S05-regex.pod Log Message: --- [S05] prefer term frugal to eager/minimal

[perl #77750] [BUG] Internal Parrot error when parsing '::' as a sole term in Rakudo

On Thu Sep 09 06:45:39 2010, masak wrote: ash_ rakudo: say ::.^methods # p6eval rakudo 859f2d: OUTPUT«===SORRY!===␤ResizablePMCArray: Can't pop from an empty array!␤» * masak submits rakudobug masak interesting error. masak rakudo: :: p6eval rakudo 859f2d:

[perl #100136] now term failing on i386

/app/projects/report_details/23389, you will notice that for recent i386 reports t/spec/S02-types/instants-and-durations.t and t/spec/S32-temporal/Date.t are failing. On my two i386 machines ./perl6 -e 'my $x = now' was hanging. The term now is defined in src/core/Instant.pm and depends

[perl #77750] [BUG] Internal Parrot error when parsing '::' as a sole term in Rakudo

# New Ticket Created by Carl Mäsak # Please include the string: [perl #77750] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=77750 ash_ rakudo: say ::.^methods # p6eval rakudo 859f2d:

[perl #58258] [BUG] The Rakudo REPL has no long-term memory

Both of the issues raised in this ticket work in the REPL (at least as of Atlanta.) Assigning to moritz++ for tests. -- Will Coke Coleda

[perl #71194] [BUG] 'self()' is parsed as a call to the term 'self', not to a function self, in Rakudo

but without the parenthesis the built-in takes precedence, if it's parsed as term (and not as function) moritz_ std: self ~~ 1 p6eval std : ok 00:01 106m␤ moritz_ std: sub a { }; a ~~ 1 p6eval std : ===SORRY!===␤Preceding context expects a term, but found infix ~~ instead [...] moritz_

[perl #62122] ~ in regexes doesn't allow braces as the last term

'(' ~ ')' 'a'* parses and does what I mean, but when I replace the last term with ['a'*] it fails to parse. Looks like a bug in PGE's parser, I'll look into this in a day or so. Thanks, Pm

[perl #62122] ~ in regexes doesn't allow braces as the last term

mean, but when I replace the last term with ['a'*] it fails to parse. Cheers, Moritz -- Moritz Lenz http://perlgeek.de/ | http://perl-6.de/ | http://sudokugarden.de/

[perl #58258] The Rakudo REPL has no long-term memory

# New Ticket Created by Carl Mäsak # Please include the string: [perl #58258] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=58258 Variables are not kept from one line to the other. r30452: $ ./perl6 my $greeting =

[perl #42429] [BUG]: docs/configuration.pod: Confusing use of term 'test'

On Fri Apr 27 19:03:28 2007, jkeen !-- x -- at verizon.net wrote: Feedback requested on patch attached. Having heard no objections, patch was applied tonight in r18417. kid51

[perl #42429] [BUG]: docs/configuration.pod: Confusing use of term 'test'

Closing ticket.

[perl #42429] [BUG]: docs/configuration.pod: Confusing use of term 'test'

On Tue Apr 10 18:50:18 2007, [EMAIL PROTECTED] wrote: There are two points in docs/submission.pod where the word 'test' is used is a way which, IMHO, is confusing. It probably would have been more productive if I had correctly identified the file I was complaining about. The file in

[perl #42429] [BUG]: docs/configuration.pod: Confusing use of term 'test'

Feedback requested on patch attached. Index: docs/configuration.pod === --- docs/configuration.pod (revision 18348) +++ docs/configuration.pod (working copy) @@ -21,11 +21,12 @@ Ffoo.pm uses Fbar_c.in, Fbar_c.in should be

[perl #42429] [BUG]: docs/submission.pod: Confusing use of term 'test'

in the second line to indicate the possessive rather than a plural. Second, you don't need both 'minus' and 'sans'; deleting 'minus' would probably be better. But, here again, the term 'test' appears in this paragraph without a preceding reference in this paragraph or the preceding one. I would

testing script using Term::ReadLine

I have a script using Term::ReadLine to get input. I'd like to test it by executing it using another script and providing answers from the script test script. I tried IPC::Run with no success but as I notice even simple redirection such as input.pl in.txt does not work. Any ideas how

Re: testing script using Term::ReadLine

On Mon, Nov 15, 2004 at 08:40:00PM +0200, Gabor Szabo wrote: I have a script using Term::ReadLine to get input. I'd like to test it by executing it using another script and providing answers from the script test script. I tried IPC::Run with no success but as I notice even simple redirection

Parrot long-term goals/prospects

I really hadn't planned on going into this now, but the issue's been raised enough that it can't be left to later. Here's the current set of long-term goals for Parrot: 1) We *will* run Perl 6, Perl 5, Ruby, Python, JVM bytecode, and .NET bytecode. Not necessarily in that order 2) [EMAIL

Re: Parrot long-term goals/prospects

On Thu, Sep 05, 2002 at 07:03:00AM -0400, Dan Sugalski wrote: 4) The *only* tools you will need to build parrot are a C compiler environment and either a make tool or a shell I believe we may be able to get away without a make tool or a shell. It won't be pretty, but I see no reason why we

Re: Parrot long-term goals/prospects

On Thu, Sep 05, 2002 at 12:12:52PM +0100, Nicholas Clark wrote: On Thu, Sep 05, 2002 at 07:03:00AM -0400, Dan Sugalski wrote: 4) The *only* tools you will need to build parrot are a C compiler environment and either a make tool or a shell I believe we may be able to get away without a

RE: Parrot long-term goals/prospects

use the term shell script loosely--on Win32 it'll be a batch file, and on VMS it'll be in DCL. You get the idea. Your platform's shell script drives the C compiler (which it may ask you for path information on) to build miniparrot. Miniparrot can run more or less with ANSI C only--no platform

RE: Parrot long-term goals/prospects

On Fri, 2002-09-06 at 02:45, Brent Dax wrote: So, building Parrot ought to look something like this (for a Windows user): c:\parrot cd build c:\parrot\build win32 Are you using MS VC++? [yn] y compiler crap cut out Miniparrot build complete. Enter

Re: Near-term schedule

On Fri, Jun 07, 2002 at 11:23:56PM -0400, Dan Sugalski wrote: 2) A revamped stack system so we can support exceptions What is the intent for stacks ? -- Jason

Near-term schedule

Okay, here's the near-term schedule, stuff I'd like to get defined and working by the end of July. 1) Plain subroutines 2) A revamped stack system so we can support exceptions 3) Exceptions 4) Loading up extensions and a simple extension interface 5) Global symbol tables Doable without much

Re: [maybe PATCH] use Term::ReadLine where possible

2002 +++ Configure.plMon Jan 21 20:05:37 2002 @@ -716,7 +716,8 @@ # Term::ReadLine::Perl does a sideways scrolling single line like ksh. print $message [$c{$field}]\n; $input = $term-readline(, $c{$field}); -$term-addhistory($input) if /\S/ and !$term

Re: on the long term Configure system

Jarkko Hietaniemi wrote: The bootstrapping may take several rounds as Parrot learns ... - execute (collect output) (note that execution may not be native) I don't think these two (cross-compile and build-own-tools) are strictly compatible goals. If you are going to build your own tools and

Re: on the long term Configure system

On Tue, Sep 11, 2001 at 04:19:12PM +0300, Jarkko Hietaniemi wrote: P.S. Maybe the long term discussion should take place in perl6-build, to draw fire from the short term? Thanks for thinking about this; it'd probably be a good idea to move to perl6-build. Simon

Re: OT: pronouncing www (was: Re: ... as a term)

"foo.bar" ne "www.foo.bar" pronounce("foo.bar") eq pronounce("www.foo.bar") As in, "Surf to www.perl.org and read the new ..." sounds like "Surf to perl dot org and read the new ..." =Austin --- Tom Christiansen [EMAIL PROTECTED] wrote: The "www" in e.g., "www.netscape.com" is pronounced,

Re: OT: pronouncing www (was: Re: ... as a term)

The "www" in e.g., "www.netscape.com" is pronounced, IMO, in the same way as other useless, should-be-obvious punctuation. It's silent. Seems like something you should take up with RFC 819, or maybe with RFC 881, considering that they and their ramifying successors all seem to be in flagrant

Re: [OT] How to pronounce 'www' (was Re: ... as a term)

On Wed, 23 Aug 2000 20:58:02 -0700, Daniel Chetlin wrote: I use "dub dub dub", which I picked up at Intel. I find it much easier to pronounce quickly than anything that uses an approximant. http://x74.deja.com/[ST_rn=ps]/getdoc.xp?AN=603967285 I do like "wibbly". Or "wibble". It has a

OT: pronouncing www (was: Re: ... as a term)

On Thu, 24 Aug 2000, Bart Lateur wrote: On Mon, 21 Aug 2000 18:21:00 -0700 (PDT), Larry Wall wrote: If you want to save the world, come up with a better way to say "www". (And make it stick...) "The world"? This problem only exists in English! We pronounce it something similar to "way

Re: ... as a term

On Mon, 21 Aug 2000 18:21:00 -0700 (PDT), Larry Wall wrote: If you want to save the world, come up with a better way to say "www". (And make it stick...) "The world"? This problem only exists in English! We pronounce it something similar to "way way way". -- Bart.

Re: ... as a term

I think this is fraught with peril. I'd have expected: print (1, 2, 3, ...) or die; to print 12345678910111213141516171819202122232425262728etc No, if that's what you wanted, you'd get it with print( 1, 2, 3 .. ) # RFC 24

Re: ... as a term

Larry Wall wrote: Either that, or it's a funny unary operator that can take 0 or 1 argument. But I'd be happy with just ... as a statement. Dwimming the unary operator may not be worth it. Especially since it might be confused with the binary operator. Could you make it "evaporate"

Re: ... as a term

Damian Conway wrote: I think this is fraught with peril. I'd have expected: print (1, 2, 3, ...) or die; to print 12345678910111213141516171819202122232425262728etc No, if that's what you wanted, you'd get it with print( 1, 2, 3 .. ) # RFC 24 -- John

Re: ... as a term

Larry Wall wrote: I'd entertain a proposal that ... be made a valid term that happens to do nothing, so that you can run your examples through perl -c for syntax checks. Or better, make it an official "stub" for rapid prototyping, with some way of getting a warning whenever y

Re: ... as a term

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 AND not joking, at the same time. -- John Porter We're

Re: ... as a term

The interesting thing about ... is that you have to be able to deal with it a statement with an implied semicolon: print "foo"; ... print "bar"; We already have plenty of statements with implied semicolons: print "foo"; for @list {}

Re: ... as a term

[EMAIL PROTECTED] writes: : We already have plenty of statements with implied semicolons: : : print "foo"; : for @list {} : print "bar"; Yes, we do, and I'm trying to figure out how to write a prototype for one of those. :-) / 2 : I'd have expected: : : print (1,

Re: ... as a term

[EMAIL PROTECTED] writes: : We already have plenty of statements with implied semicolons: : : print "foo"; : for @list {} : print "bar"; Yes, we do, and I'm trying to figure out how to write a prototype for one of those. :-) / 2 Under RFC 128 and the

Re: ... as a term

On Mon, Aug 21, 2000 at 01:01:20PM -0600, Nathan Torkington wrote: Larry Wall writes: I'd entertain a proposal that ... be made a valid term that happens to do nothing, so that you can run your examples through perl -c for syntax checks. Or better, make it an official "stub"

RE: ... as a term

-Original Message- From: Ed Mills [mailto:[EMAIL PROTECTED]] Excellent idea- anything to get to production faster! But don't {} or {1} sort of do the same thing? I think the point here is readability, not unique functionality. There more then one way to do it :) -Corwin

... as a term

Randal L. Schwartz writes: : if ($a == $b) { ... } # should this be string or number comparison? Actually, it's a syntax error, because of the ... there. :-) But that reminds me of something I wanted a few months ago. I'd entertain a proposal that ... be made a valid term that happens

Re: ... as a term

Excellent idea- anything to get to production faster! But don't {} or {1} sort of do the same thing? From: Larry Wall [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: ... as a term Date: Mon, 21 Aug 2000 09:09:01 -0700 (PDT) Randal L. Schwartz writes: : if ($a == $b

Re: ... as a term

On Mon, Aug 21, 2000 at 05:49:39PM -0700, Larry Wall wrote: [EMAIL PROTECTED] writes: : I take it the existing C... operator would be unaffected? Essentially. The lexer is (and will continue to be) quite aware of the difference between terms and operators. Oops, just read this. Ignore my

Re: ... as a term

Larry Wall writes: I'd entertain a proposal that ... be made a valid term that happens to do nothing, so that you can run your examples through perl -c for syntax checks. Or better, make it an official "stub" for rapid prototyping, with some way of getting a warning whenever y

Re: ... as a term

Larry Wall writes: I'd entertain a proposal that ... be made a valid term that happens to do nothing, so that you can run your examples through perl -c for syntax checks. Or better, make it an official "stub" for rapid prototyping, with some way of getting