RE: [lwip-devel] [task #7054] Clarification needed for variableinitialization

[Bill Florac]

I'm not much of a player here but I'll toss in another point since it has not 
been mentioned. There are occasions where it is necessary to call an _init 
function to restore a process to the original (or working) condition. In these 
cases, it is one can not rely on the global bss initialization. It is therefore 
generally safer (but perhaps slower and takes more code space) to explicitly 
define them in the _init code. (perhaps this could be a #define like FORCE_INIT)
 
On a similar note, I think that _init routines should be just initialization. 
And, we should have separate _start/_stop routines to start/stop various 
processes. There will be exeptions I'm sure.  And, while we are it, if an _init 
routine requires that another process _init or _start is done before it is 
called, it should make this clear in the comments.
 
Bill Florac
 

________________________________

From: address@hidden on behalf of Jonathan Larmour
Sent: Mon 7/30/2007 7:26 PM
To: Kieran Mansley; Jonathan Larmour; Simon Goldschmidt; Frédéric Bernon; David 
Empson; address@hidden
Subject: [lwip-devel] [task #7054] Clarification needed for 
variableinitialization




Follow-up Comment #16, task #7054 (project lwip):

Ah yes Frédéric, good point!

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/task/?7054>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/



_______________________________________________
lwip-devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/lwip-devel

<<winmail.dat>>