Re: Re: Flat Short of MEMORY_BLOCK

Brian Heilig wrote:
> I meant, is inline C acceptable in general?

No, it's not acceptable in general cases because it would require
users of some Eiffel compilers which don't need a C compiler
back-end to install one in order to compile this inline C.

> Is it that you don't want a Gobo user to compile some C library to 
> use Gobo

That's one reason.

> or is there some other reason for not wanting external C 
> references?

Some Eiffel compilers which don't otherwise require a
C compiler back-end might need to have one available
in order to compile code with external C reference. As
Franck already pointed out, I'm not sure that this will
work at all when compiling with SE to JVM.

> 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.

Why would you need to do that when the features are already
available in ISE's MANAGED_POINTER and when ISE already takes
care of making sure that these features work equally well
with Eiffel classic and Eiffel for .NET? Same remark with
SE to JVM.

BTW, the commonly used names in Eiffel for peek and poke
are `item' and `put'.

-- 
Eric Bezault
mailto:ericb-D6Qt/9opevxWk0Htik3J/[email protected]
http://www.gobosoft.com




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/