Re: Open source C# namespace to convert many audio formats

From: gilad (gilad_at_discussions.microsoft.com)
Date: 09/20/04 

Date: Mon, 20 Sep 2004 08:47:04 -0700

"Daniel O'Connell [C# MVP]" wrote:
 
> I will say you probably will not get away with it. Personally I would *not*
> use your library simply because its naming conventions are so at odds with
> those I am used to. It makes the library seem written by someone who does'nt
> know what he's doing.

But if you were a programmer who seriously needed the functionality of the
library, would you still balk at the style? It doesn't seem likely. You'd
probably shrug your shoulders and shake your head, and use it. And as for it
having the appearance of being "written by someone who does'nt know what
he's doing", isn't the actual code logic going to tell this rather than the
style? If I'm doing everything correctly as far as interfacing the DLLs,
construction of objects, etc, and yet decide to use a slightly different
naming convention (because it is style we're talking about here isn't it?),
doesn't that say whether or not I "know what I'm doing"? Breaking a style
convention could also be considered being a 'rebel'.

> While I understand you are used to perl's naming conventions, those *are*
> perl's naming conventions and are not a very good choice in a platform that
> doesn't use them.

Like I said, I was influenced by this style convention, not using it
explicitly. And I have alternated the Perl style in my own projects when it
suited me. Only when I have submitted to a repository like CPAN have I
conformed entirely. (Largely because the hue and cry that rang out from there
when I didn't.)

> Anyway, while I can see you're worried about shift key, a good number of
> characters you have to use commonly in C# code require shift, inclufing _.
> Whats the difference in typing
>
> something_else and somethingElse? Same number of shift presses, after all.

You got me there. I do use underscores. But I only do it where I need to
separate words for clarity (what I consider clarity anyway), so a lot of my
variables were pretty short and without the underscore (which seems to draw a
lot of criticism too; see below). The convention of C# uses long names most
times, and at least have one shift operation for every named thing.

> You classes should be clearer too, ;). Avoid using abbreviations when you
> can avoid it.

Sigh. I like abbreviations. So short, so succinct... Okay, thanks for the
comments.

Relevant Pages

  • Re: ISO Studies of underscores vs MixedCase in Ada or C++
    ... In Ada I follow the style guide and use both underscores ... I prefer the suggestion from the Ada style guide that you don't ... One more point on the topic of consistent naming of identifiers. ... the style with using different naming conventions for functions, ...
    (comp.programming)
  • Re: ISO Studies of underscores vs MixedCase in Ada or C++
    ... In Ada I follow the style guide and use both underscores ... I prefer the suggestion from the Ada style guide that you don't ... One more point on the topic of consistent naming of identifiers. ... the style with using different naming conventions for functions, ...
    (comp.lang.ada)
  • Re: ISO Studies of underscores vs MixedCase in Ada or C++
    ... In Ada I follow the style guide and use both underscores ... I prefer the suggestion from the Ada style guide that you don't ... One more point on the topic of consistent naming of identifiers. ... the style with using different naming conventions for functions, ...
    (comp.lang.cpp)
  • Re: The use of underscore characters in field naming conventions
    ... Ctrl+Left and Ctrl+Right don't work with underscores in the VBA editor ... > Arrow or Right Arrow on the keyboard when all of the text is together like ... >> There's really no right answer: naming conventions are just that, ... >> Doug Steele, Microsoft Access MVP ...
    (microsoft.public.access.tablesdbdesign)
Loading