> Hi, All
>
> We were looking at "[kernel]/lib/string.c"
> (http://lxr.linux.no/source/lib/string.c#L500)
>
> memcpy copies a part of memory to some other location
> but It will not work for all cases of overlapping
> blocks.(if the start of destination block falls
> between the source block)
>
>
sk malik wrote:
> memcpy copies a part of memory to some other location
> but It will not work for all cases of overlapping
> blocks.(if the start of destination block falls
> between the source block)
>
> while memove copes with overlapping areas.
>
> then why is memcpy present in the sources ca
sk malik wrote:
Hi, All
We were looking at "[kernel]/lib/string.c"
(http://lxr.linux.no/source/lib/string.c#L500)
memcpy copies a part of memory to some other location
but It will not work for all cases of overlapping
blocks.(if the start of destination block falls
between the source block)
w
On Aug 13 2007 11:55, sk malik wrote:
>Subject: why use memcpy when memmove is there?
>memcpy copies a part of memory to some other location
>but It will not work for all cases of overlapping
>blocks.(if the start of destination block falls
>between the source block)
>
>wh
Hi, All
We were looking at "[kernel]/lib/string.c"
(http://lxr.linux.no/source/lib/string.c#L500)
memcpy copies a part of memory to some other location
but It will not work for all cases of overlapping
blocks.(if the start of destination block falls
between the source block)
while memove copes
5 matches
Mail list logo