Programming Convention Survey of the day

[Jasmine2501]

1 makes the most sense, but the thing is written wrong in the first place. It should be: Array.CopyTo(Record r) and/or: Record.CopyFrom(Array a)

"Quality Software since 1983!"
http://www.smoothjazzy.com/ - see the "Programming" section for freeware tools and articles.

[Owen37]

Ahhh, the little-endian/big-endian question again. Doesn't really matter what the order is. However, your department should pick one -endian naming convention and stick to it. Cheers, Owen

[Dwayne J Baldwin]

I expect #1. What makes most sense is to never allow a developer to make this decision in the first place. Class Record Copy(array) Parameter lists are evil, period.

Dwayne J. Baldwin

[Yortw]

1. array, record ... dunno why but I always expect source before destination.

[Lost User]

#1--What did I when? And are ya ever gonna tell us your point?

____________________________________________________________________________ "Space is big. You just won't believe how vastly, hugely, mind- bogglingly big it is. I mean, you may think it's a long way down the road to the chemist's, but that's just peanuts to space." -- Douglas Adams -- Shohom67

[Paolo Pagano]

What about make the whole signature (parameters names too) tell about semantic? CopyTo( Object[] source, Record destination ) This can be lighter to use: array.CopyTo( record ) my fear is that people tend abuse naming, I saw around names like: CopyFirstObjectArrayParameterToSecondRecordParameter :wtf:

pp

[steve teng]

why isn't 2? I like 2!;P

[Rick Shaub]

As long as the types are different and the parameter names are sufficiently descriptive, I don't think it matters.

[Abdellatif_El_Khlifi]

1 is more logical ;)

[destynova]

It's "believe", not "belive". Your name is massive AND a typo!