camelcase vs. lower case

[epitka]

So if I set my default to be nosetter.camelcase-underscore as access
strategy, if I happen to have an attribute name that is not a
"camelcasable" like _end or _start I have to specify explicitly that
these are nosetter.lowercase-underscore? Not sure if this is NH of
FluentNH, but I would expect lowercase to be fallback for camelcase.
Does that make sense?

[James Gregory]

Yes, you have to specify it. The problem with NH trying to read your mind is your assumptions of what should and shouldn't be fallbacks might differ to what others think.

[epitka]

ok, just wanted to make sure before trying to chase it around.

On Mar 27, 4:25 pm, James Gregory <jagregory....@gmail.com> wrote:
> Yes, you have to specify it. The problem with NH trying to read your mind is
> your assumptions of what should and shouldn't be fallbacks might differ to
> what others think.
>

[TigerShark]

I'm not sure I entirely understand your question, but your example are
perfectly camelcase (unless you decide to spell "end" as "eNd" or
something similar).

I have numerous short names like that in my classes and I've never had
a problem with NH understanding my naming strategy as camelcase-
underscore. What it basically comes down to is the naming convention
based on your property. As I don't believe you have public fields
named like that, your properties would be translated like this with
nosetter/field.camelcase-underscore:

"End" -> "_end"
"Start" -> "_start"

Remember that camelcase differs from pascalcase only by the first
letter being lowercase with camelcase and uppercase with pascalcase.

But then again, I could have read your question wrong ;)