Re: Doubt in memcpy() and memset()
- From: Kenneth Brody <kenbrody@xxxxxxxxxxx>
- Date: Wed, 06 Dec 2006 10:42:55 -0500
Tom St Denis wrote:
Random832 wrote:
yeah, but the size argument changed types. certainly nothing promotes to
a size_t, and there's no guarantee that size_t doesn't promote to
something.
Does it matter? Most platforms won't let you push a char on the stack
anyways (disregarding the fact the standard makes no mention of
"stack").
So from a performance point of view it's moot.
No, but if you are passing an int rather than unsigned char, it
may need to zero-fill the rest of the int before passing it.
--
+-------------------------+--------------------+-----------------------+
| Kenneth J. Brody | www.hvcomputer.com | #include |
| kenbrody/at\spamcop.net | www.fptech.com | <std_disclaimer.h> |
+-------------------------+--------------------+-----------------------+
Don't e-mail me at: <mailto:ThisIsASpamTrap@xxxxxxxxx>
.
- Follow-Ups:
- Re: Doubt in memcpy() and memset()
- From: Tom St Denis
- Re: Doubt in memcpy() and memset()
- References:
- Doubt in memcpy() and memset()
- From: Shhnwz.a
- Re: Doubt in memcpy() and memset()
- From: Chris Dollin
- Re: Doubt in memcpy() and memset()
- From: Dead Loop
- Re: Doubt in memcpy() and memset()
- From: Lew Pitcher
- Re: Doubt in memcpy() and memset()
- From: Random832
- Re: Doubt in memcpy() and memset()
- From: Tom St Denis
- Doubt in memcpy() and memset()
- Prev by Date: Re: problem in structure
- Next by Date: Re: malloc
- Previous by thread: Re: Doubt in memcpy() and memset()
- Next by thread: Re: Doubt in memcpy() and memset()
- Index(es):
Relevant Pages
|
|