Java: CopyMemory equivalent

[Tuberload]

Storm: Thank you for the useful info. It was hard to find buried under all the other crap:)

I've been programming in Java about 8 months now and have my Oracle certification and working on getting the sun cert, but there is still a lot to learn.

[Skywing]

I suppose it would go like this:

Code Select Expand


void copymemory(void* src, void* dest, int len) {
for (int i = 0; i < len; i++) {
*dest = *src;
src++;
dest++;
}


or like this:

Code Select Expand

#define copymemory memcpy

That could cause annoying syntax errors; memcpy returns a value, while copymemory does not.

[Camel]

since when was it mandatory to recieve what a function returns?

[Skywing]

since when was it mandatory to recieve what a function returns?

It's a good idea when you're replacing a standardized function.  Besides, some C compilers have been known to warn about unchecked return values - perhaps you should use (void)memcpy.

[Grok]

Skywing you're fighting an uphill battle.  Most people are too lazy to be concerned with the proper way to do things.  Even though learning these techniques will save them and other people much aggravation in the future, the lazy ones only care that their code compiles right now.  Nevermind all the problems that come with being a crappy programmer and distributing crappy code.  If it compiles and runs today, it's all they need or care about, right?

[tA-Kane]

Nevermind all the problems

As the saying goes, "I'll cross that bridge when I get there."

[Banana fanna fo fanna]

Or we could just use memcpy and be happy.

[Camel]

good call, storm
+1

[Banana fanna fo fanna]

DAMN, MORE KARMA