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

From: TSa <[EMAIL PROTECTED]> Date: Tue, 12 Aug 2008 09:25:27 +0200 . . . What's so different in $foo-bar versus $foo*bar, $foo+bar or $foo/bar? The latter might e.g. indicate path variables. FWIW, one sees "hyphen substitution" like this only very rarely in Common Lisp code, desp

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

On 2008 Aug 12, at 20:39, Austin Hastings wrote: Actually, I proposed some years ago allowing "separable verbs" -- function/method/operator names with spaces in them, that could in fact bracket or intersperse themselves with other parameters. This would be a way of writing "if ... elsif ..

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

Actually, I proposed some years ago allowing "separable verbs" -- function/method/operator names with spaces in them, that could in fact bracket or intersperse themselves with other parameters. This would be a way of writing "if ... elsif ... else ..." for example. I wonder if whitespace in id

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

Mark J. Reed wrote: On Tue, Aug 12, 2008 at 4:03 AM, Michael Mangelsdorf <[EMAIL PROTECTED]> wrote: relaxed identifiers could become what programmers actually expect. Relaxing the rules is fine, but I would like to state for the record that I'd rather not ever see whitespace allowed in identif

Re: [svn:perl6-synopsis] r14574 - doc/trunk/design/syn

The ' is actually a letter in some writing systems (e.g. Hawai'ian), and contractions are extremely common in French compared to English. $l'etat = "moi". But even in English I'll like being able to spell contractions properly. Hey, maybe we could borrow from Intercal and allow the "commenting o

RE: r14574 - doc/trunk/design/syn

> On 8 Aug., 19:34, Ron wrote: > > Author: larry > > Date: Fri Aug  8 10:34:49 2008 > > New Revision: 14574 > > > > Modified: > >    doc/trunk/design/syn/S02.pod > > > > Log: > > allow isolated ' and - in identifiers (only if followed by alpha) > > While I understand why - in identifiers is The Ri

Re: [perl #57756] Implementation of .subst for strings in rakudo

Just tracked down a slight braino in the Str implementation of subst. The new attached patch fixes this. subst-oops.patch Description: Binary data

interpreter persistence issues

i'd like to have an option in mod_parrot to clear all user-generated data (globals, namespaces, subs, etc.) from an interpreter, leaving any bytecode that has been loaded (e.g. compilers). the point here is to eliminate problems caused by data persistence on hosted web servers, which is one of

[perl #57668] [BUG][PATCH] Iterate through the current namespace causes a segfault

On Wed Aug 06 12:51:02 2008, fperrad wrote: > The patch contains a test case that exhibits the problem. > > François. Applied in r30181, as a TODO test. François.

Re: Multiple Return Values - details fleshed out

On 2008-Aug-9, John M. Dlugosz wrote to clarify and extrapolate from what is written in the Synopses: Third, list assignment will handle assignment to a literal pair by accessing the names of the items inside the Capture. So list assignment beh

Re: r14574 - doc/trunk/design/syn

On 8 Aug., 19:34, [EMAIL PROTECTED] wrote: > Author: larry > Date: Fri Aug  8 10:34:49 2008 > New Revision: 14574 > > Modified: >    doc/trunk/design/syn/S02.pod > > Log: > allow isolated ' and - in identifiers (only if followed by alpha) While I understand why - in identifiers is The Right Thing

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

On Tue, Aug 12, 2008 at 4:03 AM, Michael Mangelsdorf <[EMAIL PROTECTED]> wrote: > relaxed identifiers could become what programmers actually expect. Relaxing the rules is fine, but I would like to state for the record that I'd rather not ever see whitespace allowed in identifiers. That's an Apples

Re: [perl #47972] [DEPRECATED] getclass opcode

On Tue, Aug 12, 2008 at 02:14:07PM +0200, Allison Randal wrote: > Will Coleda wrote: >> I agree that any removed feature should have a deprecation cycle; >> Here's my pitch for how we've already done that; the list of >> deprecated features has RTs; the RT listed what was going to have to >> happen

[perl #57814] Bug Report: Error running make on Red Hat Enterprise v 3.6.9

# New Ticket Created by "Paul Gibler" # Please include the string: [perl #57814] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=57814 > src/main.o(.text+0x5c): In function `main': src/main.c:52: undefined reference to `Parr

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

Nicholas Clark nick-at-ccl4.org |Perl 6| wrote: Also, in Perl 6, constants aren't going to be bare words, because unlike Perl 5, they're not going to be implemented as subroutines. So that's another "obvious" thing that actually isn't going to matter here. A C in Perl 6 can be declared with or

Re: Inter-HLL Mapping Notes

The simple answer is Parrot won't do any automatic mapping of types between HLLs. If you call a Python library function that returns a Python Dictionary type, you'll get back a Python Dictionary PMC. You can interact with it as a string keyed hash (because it implements the string keyed vtable

Re: [perl #47972] [DEPRECATED] getclass opcode

Will Coleda wrote: I agree that any removed feature should have a deprecation cycle; Here's my pitch for how we've already done that; the list of deprecated features has RTs; the RT listed what was going to have to happen for some time now; This covers us on the deprecation notification. I am w

Re: [perl #47972] [DEPRECATED] getclass opcode

On Tue, Aug 12, 2008 at 2:39 AM, Patrick R. Michaud via RT <[EMAIL PROTECTED]> wrote: > On Mon Aug 11 18:10:30 2008, coke wrote: >> >> 'getclass' is dead, patch applied in r30176. All tests pass. > > r30176 (and it's subsequent fix for builtins.h in r30179) cause Rakudo > to stop building with: > >

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

On Mon, Aug 11, 2008 at 09:07:33AM -0400, Mark J. Reed wrote: > I'm still somewhat ambivalent about this, myself. My previous > experience with hyphens in identifiers is chiefly in languages that > don't generally have algebraic expressions, e.g. LISP, XML, so it will > take some getting used to i

Porting the parrot website

We could use a few volunteers to port pages from parrotcode.org to the new Parrot website. It's a simple repetitive task, view source on the original page and paste the main HTML into the new CMS. (Ignoring any pages automatically generated from Pod in the repository, because we'll handle those

[perl #47956] [BUG] :init :load cannot be target of :outer in compiled PIR

An update for this ticket post-pdd25cx merge: Attempting to run y.pir (described earlier in this ticket) now produces a segfault. Here's the output on my system as of r30182 in trunk: $ ./parrot y.pir compiler start reading x.pir into $S0 compiling (but not running) $S0 XYZ::BEGIN src/inter_call

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

Dear Thomas, >>Is this supposed to be a joke Absolutely not. What I was trying to say is that there seems to be a trend to consider very relaxed identifier rules a good thing. If Perl 6 wants to grab the road for 20 years, then perhaps this issue is more serious (this is why I quoted you in par

Re: YAPC::EU 2008

"Wherever two or more of you are gathered together..." Bernhard and I are currently in the lobby at Hotel Centrum, 2 blocks south-west from the main train station (Kobenhavns H) on the corner of Istedgade and Helgolandsgade. Free wireless is available. Will send an update if the location chan

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

HaloO, Michael Mangelsdorf wrote: Actually I can even imagine allowing almost all chars in the middle of identifiers. Is this a trend we should extrapolate into the lifetime scope of the Perl 6 language? How far are we in this process, given Unicode guillemets for hyper ops? Is this supposed