Programming Convention Survey of the day

[W Balboos GHB]

I'm believe the name "everynameiwant" is still available.

"Shoes For Industry!" - G. Tirebiter

[W Balboos GHB]

I prefer (1) as it is intuitive. On the other hand, before I even learned C I learned some Assembly - and got rather used to the target, source order. It was kept constant, and thus did not boggle the mind with inconsistencies. Not so fast: However, (2) has the following going for it: The best way would be to handle this by keeping the setup consistant within a given family of functions (methods, or whatever). Often this means putting the target first, and than various arguement sets would follow (called overloading these days). I do tend to like this consistency of form that target, params allows.

"The difference between genius and stupidity is that genius has its limits." - Albert Einstein

[M i s t e r L i s t e r]

CopyObjectArrayToRecord( array, record )

[M i s t e r L i s t e r]

in addition, when using COM for IDispatch programming, the last parameter is usually used as the return value... so your convention follows a common practice.

[pgorbas]

The obvious order to me is the order in which the terms are written - so number 1 - the from term Array then 2- the to term records. If someone wanted it the other way they should name the method CopyRecordFromObjectArray.

[deltalmg]

All programming languages are "modern", we aren't talking about ancient arimaic or something :) int IfItAnitBroke(void[] *, void[] *) // todo make obscure as hell so nobody copies my idea

[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!