Re: [perl6/specs] a7cfe0: [S32] backtraces overhaul

2011-08-24 Thread Parrot Raiser
S19 uses hyphens for all of perl6's long-form command-line flags. Command-line flags and methods are separate sets. Hyphens would be the norm for flags. In S28, we find $*EXECUTABLE_NAME and %*META-ARGS listed within 10 lines of each other. S32-setting-library_IO.pod and

Re: [perl6/specs] a7cfe0: [S32] backtraces overhaul

2011-08-24 Thread Mark J. Reed
That kind of consistency is not much better than inconsistency in terms of usability, IMO. I'd much prefer a purely lexical convention that doesn't rely on how you assign parts of speech or define a single word that has a hyphen in it. Given that we allow hyphens in identifiers, I'd personally

Re: [perl6/specs] a7cfe0: [S32] backtraces overhaul

2011-08-23 Thread Damian Conway
It's a trivial point, but why hidden_from_backtrace instead of hidden-from-backtrace? Especially given that the associated method is is-hidden, not is_hidden? Are we consistently using underscores for multi_word traits and hyphens for multi-word methods? Wouldn't it be nice to have a consistent

Re: [perl6/specs] a7cfe0: [S32] backtraces overhaul

2011-08-23 Thread Moritz Lenz
Am 23.08.2011 10:46, schrieb Damian Conway: It's a trivial point, but why hidden_from_backtrace instead of hidden-from-backtrace? Especially given that the associated method is is-hidden, not is_hidden? The current stance seems to be that low-level things are spelled with underscores, while

Re: [perl6/specs] a7cfe0: [S32] backtraces overhaul

2011-08-23 Thread Moritz Lenz
Am 23.08.2011 10:56, schrieb Moritz Lenz: And why is this entire message written in questions? Is it? I'm afraid I don't understand what you mean. Never mind?

Re: [perl6/specs] a7cfe0: [S32] backtraces overhaul

2011-08-23 Thread philippe.beauch...@bell.ca
: Tuesday, August 23, 2011 04:56 AM To: perl6-language@perl.org perl6-language@perl.org Subject: Re: [perl6/specs] a7cfe0: [S32] backtraces overhaul Am 23.08.2011 10:46, schrieb Damian Conway: It's a trivial point, but why hidden_from_backtrace instead of hidden-from-backtrace? Especially given

Re: [perl6/specs] a7cfe0: [S32] backtraces overhaul

2011-08-23 Thread Richard Hainsworth
@perl.org Subject: Re: [perl6/specs] a7cfe0: [S32] backtraces overhaul Am 23.08.2011 10:46, schrieb Damian Conway: It's a trivial point, but why hidden_from_backtrace instead of hidden-from-backtrace? Especially given that the associated method is is-hidden, not is_hidden? The current stance seems

Re: [perl6/specs] a7cfe0: [S32] backtraces overhaul

2011-08-23 Thread philippe.beauch...@bell.ca
:613-327-6928 - Original Message - From: Richard Hainsworth [mailto:rich...@rusrating.ru] Sent: Tuesday, August 23, 2011 06:28 AM To: perl6-language@perl.org perl6-language@perl.org Subject: Re: [perl6/specs] a7cfe0: [S32] backtraces overhaul If you're asking for an explanation

Re: [perl6/specs] a7cfe0: [S32] backtraces overhaul

2011-08-23 Thread Mark J. Reed
: Richard Hainsworth [mailto:rich...@rusrating.ru] Sent: Tuesday, August 23, 2011 06:28 AM To: perl6-language@perl.org perl6-language@perl.org Subject: Re: [perl6/specs] a7cfe0: [S32] backtraces overhaul If you're asking for an explanation of the humour, then it's easy. There is no word play

Re: [perl6/specs] a7cfe0: [S32] backtraces overhaul

2011-08-23 Thread Damian Conway
The current stance seems to be that low-level things are spelled with underscores, while we reserve the minus character for user-space code. Try grepping the specs for identifiers of built-ins that have a minus in it -- I didn't find any in a quick search. I had a little more time to look and

Re: [perl6/specs] a7cfe0: [S32] backtraces overhaul

2011-08-23 Thread Patrick R. Michaud
On Tue, Aug 23, 2011 at 05:36:27PM +0200, Damian Conway wrote: And I'd like there to be a more consistent approach than that (though I don't really care what it actually is). +1 to consistency. Pm