I'd much rather see a single consistent style throughout the setting than backwards compatibility with p5 naming conventions.
If Temporal is the first setting module to use multiword identifiers, I vote for hyphens. They're easier on the fingers and the eyes; underscores have always felt like an ugly compromise to make the compiler's job easier. On Saturday, April 10, 2010, Carl Mäsak <cma...@gmail.com> wrote: > John (>): >> Forgive me if this is a question the reveals how poorly I've been >> following Perl 6 development, but what's the deal with some methods >> using hyphen-separated words (e.g., day-of-week) while others use >> "normal" Perl method names (e.g., set_second)? > > I'd just like to point out that the current Temporal spec only does > methods with underscores, including C<day_of_week>. > > This goes against my personal preferences; I greatly prefer dashes in > almost all of the code I write. But I acknowledge that most of the > programmers out there seem to expect underscores -- and also, the aim > was to produce a small delta from CPAN's DateTime and not change > around things ad lib. > > // Carl > -- Mark J. Reed <markjr...@gmail.com>
