Re: YY_SCANNER_SKELETON.yy_content_area could be ABSTRACT_SPECIAL ?

Berend de Boer wrote:
>>>>>> "Eric" == Eric Bezault <[email protected]> writes:
> 
>     Eric> In my mind, it has always been clear that we should use
>     Eric> SPECIAL for efficency reason. The reason why this could be
>     Eric> bypassed is that at the time of writing some of the
>     Eric> supported Eiffel compilers did not support SPECIAL. Using
>     Eric> ABSTRACT_SPECIAL is not really a solution because it
>     Eric> introduces polymorphism, hence reducing the performance that
>     Eric> we want to gain by using SPECIAL directly.
> 
> But with SPECIAL comes the need for a copy. Which is a bit slow
> especially in debug mode. It's not a huge problem, but it would be
> nice if SPECIAL had a fast way to copy data from a given pointer.

In all cases that I had so far, there was no need to copy to a
SPECIAL because the SPECIAL was already available. Hence the
optimization. I had not faced the problem you have with a pointer
because I always try to write pure Eiffel, hence no pointer to
deal with.

-- 
Eric Bezault
mailto:[email protected]
http://www.gobosoft.com

------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing 
server and web deployment.
http://p.sf.net/sfu/businessobjects