Re: next pass of cleaning up micropatch.c

2 messages, 2 authors, 2004-10-08 · open the first message on its own page

Re: next pass of cleaning up micropatch.c

From: Wolfgang Denk <hidden>
Date: 2004-10-08 22:32:49

In message [off-list ref] you wrote:
nice idea, but sadly, doomed to failure.  note that the code to copy 
the patch arrays *requires* you to be able to take the sizeof() those 
arrays to know *exactly* how much to copy.  if you pass the array to a 
function by its address, i'm pretty sure you lose the ability to take 
its sizeof() anymore, isn't that right?
This is not right. Guess how memcpy() works - it's a function, btw.

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
God runs electromagnetics by wave theory on  Monday,  Wednesday,  and
Friday,  and the Devil runs them by quantum theory on Tuesday, Thurs-
day, and Saturday.                                   -- William Bragg

Re: next pass of cleaning up micropatch.c

From: Robert P. J. Day <hidden>
Date: 2004-10-08 23:16:54

On Sat, 9 Oct 2004, Wolfgang Denk wrote:
In message [off-list ref] you wrote:
quoted
nice idea, but sadly, doomed to failure.  note that the code to copy
the patch arrays *requires* you to be able to take the sizeof() those
arrays to know *exactly* how much to copy.  if you pass the array to a
function by its address, i'm pretty sure you lose the ability to take
its sizeof() anymore, isn't that right?
This is not right. Guess how memcpy() works - it's a function, btw.
sure.  and it accepts a size parameter, which is why it works.  i'm 
not sure what you're getting at.

rday
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help