Re: [gobo-eiffel-develop] Object-oriented byte-codes for regularexpressions?

[Eric B. <er...@go...>]

CRISMER Paul-Georges wrote:
> What is the "cost" you are ready to pay for?
> 
> - OO / Single choice :
>   cost of non-expandedness + dynamic binding (time)
>   benefit of readability (development effort)
> 
> - Integer (instruction number) + giant inspect
>   cost - readability (development effort)
>   benefit - run-time efficiency (time)

Assuming that from the client point of view they
have the same interface (only the implementation
differs), as a client of the library I'm only
concerned in speed and memory usage. And specially
in case of regexp. When there is a trade-off to be
made, the client should be the winner. That's what
happen for the Eiffel language itself: put the burden
on the compiler writers, not on the language users.
Now you might say that compiler writers should make
it so that the cost of non-expandedness + dynamic binding
should not be noticeable compared to giant inspect ;-)

-- 
Eric Bezault
mailto:er...@go...
http://www.gobosoft.com