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 like to see them used everywhere, for all identifiers defined at the p6 level. Lower-level names that are just called from p6 are of course another matter. I could also see substituting underscores for hypens in all-caps names for ease of typing (at least, that'd be easier on US keyboards). On Tuesday, August 23, 2011, Parrot Raiser <1parr...@gmail.com> wrote: >> 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 S32-setting-library_Numeric.pod each have >> public multi-word method names with hyphens. > > In both cases, hyphens are linking qualifying adjectives to nouns, > while hyphens separate distinct words. One could argue that is not > inconsistent. > > On 8/23/11, Patrick R. Michaud <pmich...@pobox.com> wrote: >> 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 >> > -- Mark J. Reed <markjr...@gmail.com>
