<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I'm mostly a listener on the mailing list but I very much agree with
Walter. Personally I think arguments about typing length are daft in
an age with IDEs and language tooling. The most important aspect of
the naming convention IMHO is readability and intuitiveness. I like
the idea of naming the functions in different modules with the same
pattern if they complete the same task (albeit in different ways or
on different types of data... etc).<br>
<br>
There's a lot of options for disambiguating naming clashes in the
language:<br>
<ul>
<li>aliasing</li>
<li>renamed imports</li>
<li>selective importing from a module<br>
</li>
<li>fully qualified names (e.g. std.ascii.toLower() )<br>
</li>
</ul>
That's my two cents,<br>
<br>
Chris<br>
<br>
<br>
On 06/22/11 17:53, Walter Bright wrote:
<blockquote cite="mid:itt6vi$2ckn$1@digitalmars.com" type="cite">On
6/22/2011 4:47 AM, Lars T. Kyllingstad wrote:
<br>
<blockquote type="cite">One problem: std.uni only contains
functions for dealing with upper/
<br>
lower case and for checking whether something is an alpha
character. If
<br>
you want the other functions, such as isDigit(),
isPunctuation(), etc.
<br>
you still have to import std.ascii. And once you have imported
both
<br>
std.uni and std.ascii, you are forced to disambiguate every time
you call
<br>
a function which exists in both.
<br>
</blockquote>
<br>
True, but I don't see much of an improvement of:
<br>
<br>
toAsciiLower()
<br>
<br>
over:
<br>
<br>
std.ascii.tolower()
<br>
<br>
at least as far as typing goes.
<br>
</blockquote>
</body>
</html>