Re: Flat Short of MEMORY_BLOCK

Franck Arnaud wrote:
> Brian Heilig:
> 
> > Is inline c acceptable?
> 
> Inline C won't work with Smarteiffel producing 
> JVM output, also VE does not produce C code or use 
> a C compiler directly, so you'd need an extra C 
> compiler in the loop.

I meant, is inline C acceptable in general?

Eric,
Is it that you don't want a Gobo user to compile some C library to 
use Gobo, or is there some other reason for not wanting external C 
references? Assuming there were no other technical difficulties, 
would you allow inline C code?

Franck,

If MANAGED_POINTER were built using gepp (which I think it will be) 
you could use inline C code for ISE for all of the peek/poke 
functions. This would avoid the overhead of calling memory_copy. Is 
there an issue with using inline C code for an ISE specific 
MANAGED_POINTER?

All,
I forgot to mention the following SmartEiffel feature to peek an 8-
bit integer:

--- SE
from class NATIVE_ARRAY
item(index: INTEGER): E

Where E is of type INTEGER_8.

Brian



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/