FLTK native in 'D'. Would that be useful?

[MatthiasM]

Sean Kelly wrote:
>>
>> One other note on this <g> If a member function needs to be protected 
>> or public but is not to be overridden, it can be made 'final'. Then 
>> the compiler will always call it directly and it can be inlined, etc.
> 
> Yup.  In general, all C++ functions that are not virtual should be 
> marked 'final' in D.  Also, any private virtual functions must be made 
> protected instead.

I see. I do not want to finalize too many functions, simply because I 
have stumbled over a few functions in FLTK that I would love to have 
virtual, but can't change it anymore in FLTK1.1.x because we are keeping 
binary compatibility within a branch, and we are not ready yet to open a 
true 1.2 ;-)

Matthias

PS: I am really interested in what the performance of the "D" code will 
be. It won't matter too much for FLTK itself, but eventually, should I 
port my Robotics simulation, performance is a requirement.