Re: Flat Short of MEMORY_BLOCK

> Eric Bezault wrote:
>
> But why not using the regular Eiffel code all the time?
> At least we won't have to modify our #ifdefs when an Eiffel
> compiler which used to require a C compiler adds a compilation
> mode for which it is not the case anymore.

I agree. The code provided by the compilers is the most portable. If 
we want a Gobo solution, then we want something that is highly 
portable and simple. If someone really wants speed they can 
implement YET_ANOTHER_BUFFER_CLASS.

> I cannot see why user-written C code could be faster
> than the equivalent functionality provided by the
> compilers when they require a C compiler as back-end.
> If it was faster to write inline C code, that's what
> the Eiffel compiler should have provided in its Eiffel
> class, no?

Because:

buffer[i] = a_byte;

is faster than:

memcpy (&buffer[i], &a_byte, 1);

SmartEiffel is probably the only one that will use the former due to 
its NATIVE_ARRAY.

Brian



------------------------ Yahoo! Groups Sponsor ---------------------~-->
Buy Ink Cartridges or Refill Kits for your HP, Epson, Canon or Lexmark
Printer at MyInks.com. Free s/h on orders $50 or more to the US & Canada.
http://www.c1tracking.com/l.asp?cid=5511
http://us.click.yahoo.com/mOAaAA/3exGAA/qnsNAA/saFolB/TM
---------------------------------------------------------------------~->

To Post a message, send it to:   [email protected]
To Unsubscribe, send a blank message to: [email protected] 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
     http://groups.yahoo.com/group/gobo-eiffel/

<*> To unsubscribe from this group, send an email to:
     [email protected]

<*> Your use of Yahoo! Groups is subject to:
     http://docs.yahoo.com/info/terms/