> 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 found... S12 describes Attribute objects as having a method named 'has-accessor', but also having a method named 'get_value'. S19 uses hyphens for all of perl6's long-form command-line 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. And both also list other identifiers that use underscores. I'm not sure I'm seeing the pattern, though. Apart perhaps from "older parts of the spec use underscores, newer parts use hyphens". And I'd like there to be a more consistent approach than that (though I don't really care what it actually is). Damian
