Programming Convention Survey of the day

[Thunderbox666]

So which one should we be agreeing with?

"There are three sides to every story. Yours, mine and the truth" ~ unknown

[Marc Clifton]

Well, bucking the trend (as usual), whatever it's called, I would expect the destination (target) object to be the first parameter. So, #2! :-D [edit]And sadly, in C#, Array.Copy takes the source array as the first parameter. Which leads me to end of teeth gnashing because I liked the platform SDK's consistency of having the destination as the first parameter, such as in the BitBlt function or, in the C/C++ language, another example is the memcpy function. So, here's another perfect example of how the designers of C# BLEW IT!!![/edit] Marc

Thyme In The Country
Interacx
My Blog

[martin_hughes]

I use Intellisense, earn lots of money, sleep in a big comfy bed with my wife and don't tend to worry about these things :)

Me: Can you see the "up" arrow? User:Errr...ummm....no. Me: Can you see an arrow that points upwards? User: Oh yes, I see it now! -Excerpt from a support call taken by me, 08/31/2007

[Shog9 0]

Marc Clifton wrote:

Well, bucking the trend (as usual), whatever it's called, I would expect the destination (target) object to be the first parameter.

Wouldn't you call it IntoRecordCopyObjectArray() then... ;P

every night, i kneel at the foot of my bed and thank the Great Overseeing Politicians for protecting my freedoms by reducing their number, as if they were deer in a state park. -- Chris Losinger, Online Poker Players?

[Shog9 0]

Bah! Madness! record.AddCopyOfObjectArray(array)

every night, i kneel at the foot of my bed and thank the Great Overseeing Politicians for protecting my freedoms by reducing their number, as if they were deer in a state park. -- Chris Losinger, Online Poker Players?

[Rama Krishna Vavilala]

1

Co-Author ASP.NET AJAX in Action

[Hans Dietrich]

Rama Krishna Vavilala wrote:

Just based on the name what do you expect the order of parameters to be

I wouldn't have any expectation - I would look at the definition. :) You could make a case for either one. For example, the CRT has functions

char *strcpy( char *strDestination, const char *strSource );

void *memcpy( void *dest, const void *src, size_t count );

while Win32 has function

VOID CopyMemory(PVOID Destination, CONST VOID* Source, SIZE_T Length);

but also has function

BOOL CopyFile(LPCTSTR lpExistingFileName, LPCTSTR lpNewFileName, BOOL bFailIfExists);

I think the more important question is, what do other functions in your namespace do? It would be a source of confusion/bugs if one function did it one way, while all others did it another way.

Best wishes, Hans

---

[CodeProject Forum Guidelines] [How To Ask A Question] [My Articles]

[Marc Clifton]

Shog9 wrote:

Wouldn't you call it IntoRecordCopyObjectArray() then...

Nah. In fact, I'd just call it "Copy" and let the args tell me what its copying and from and to. Marc

Thyme In The Country
Interacx
My Blog

[Shog9 0]

Marc Clifton wrote:

In fact, I'd just call it "Copy" and let the args tell me what its copying and from and to.

Yeah, that's probably the least idiotic method. So long as you don't, say, wrap your static copy method in the wrong class...

every night, i kneel at the foot of my bed and thank the Great Overseeing Politicians for protecting my freedoms by reducing their number, as if they were deer in a state park. -- Chris Losinger, Online Poker Players?

[Thunderbox666]

:) good thing i said #1 then

"There are three sides to every story. Yours, mine and the truth" ~ unknown

[Jim Crafton]

Phil Martin... wrote:

I were in C (and not C++)

I think you mean: int obj_rec_n_cpy(void*, void*, int);

¡El diablo está en mis pantalones! ¡Mire, mire! Real Mentats use only 100% pure, unfooled around with Sapho Juice(tm)! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! VCF Blog

[idontbelivethateverynameiwantistaken]

True that.

Zakk Of all Trades

[_Damian S_]

LMFAO... surely you could find one name that wasn't taken? How about ihavetheworldslongestscreennameanditshardtoread

------------------------------------------- Don't walk in front of me, I may not follow; Don't walk behind me, I may not lead; Just bugger off and leave me alone!!

[DaveX86]

This convention actually drives me crazy...it should be from left to right to keep the flow natural...assembly language does it like that: MOV dst, src ...no wonder nobody uses it. It's like reading a sentence that you have to start at the beginning, then jump to the end and read back to the middle...an unnecessary direction change. :~

[Robert Surtees]

David Lockwood wrote:

...it should be from left to right to keep the flow natural

So I'm guessing you would prefer 3 = a over a = 3 to assign 3 to a? :)

[DaveX86]

Well..hmmm...if you put it that way If you put it more like MOV 3, a ...though, it does work better. It's not totally the same thing, a math equation and a computer instruction. maybe my brain is reversed...that's always been my problem :~

[Phil Martin]

Nope, I don't think I meant that.

[Ravi Bhavnani]

1 /ravi

This is your brain on Celcius Home | Music | Articles | Freeware | Trips ravib(at)ravib(dot)com

[DJ van Wyk]

I also agree with 1

[Kitty234]

Probably based on my (disappointly-small) objective-C experience, I'd see that as being: [anObject copyObjectArray: anArray toRecord: aRecord]; otherwise knows as: anObect.copyObjectArrayToRecord(anArray, aRecord);