Hi, > On Thu, Jul 29, 2004 at 09:49:09AM +0200, Oliver Schmidt wrote: > > I would opt - as always - for dynamic runtime checking of the OS running on. > > But I'm quite sure that Ullrich won't like that - as always - because of the > > C library blow-up ;-) > > If I hear the complaints that not enough memory is available to run a flash > plugin for Contiki, I think that my concerns about code size are justified, > aren't they? :-) Please note the ' ;-)' above... BTW: In my oppinion gif support would be hard enough, but flash ??? > See my library proposal in the other mail. Which looks just great to me :-)) > Would it be possible to separate > the code so cleanly that using two or more disk I/O libs could solve the > problem? As fas as I can see: Yes. > There can be references from the main code into the disk I/O > libraries, but the interface needs to be the same for all of them. As fas as I understand this would be quite easy as they don't share code anyway but both need to implement the APIs for the stream based stuff anyway - or do I miss a point here? > Since using constructors for initialization is also an option, I think this > should work (provided that the linker is able to handle it). Again I agree. Oliver ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Thu Jul 29 10:16:38 2004
This archive was generated by hypermail 2.1.8 : 2004-07-29 10:16:47 CEST