[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kfm-devel
Subject:    Re: KJS API changes
From:       David Faure <david () mandrakesoft ! com>
Date:       2001-10-23 21:01:24
[Download RAW message or body]

On Vendredi 19 Octobre 2001 17:43, Harri Porten wrote:
> > - The typeInfo struct is also gone. Objects now return a String for
> >   their class name.
> [....]
> > - An equivalent to typeInfo is needed so that classes can be identified
> >   using a static pointer rather than a string... this will be mostly
> >   useful for testing class types in the internal functions in
> >   situations where an application's bindings permit objects named with
> >   the same class name as internal types, e.g. "Array"
> 
> Why not leave the typeInfo struct then ? I see no other way to support
> inheritance checks.

Now that Peter has re-added ClassInfo, I wonder if the UString class name
stored in every ObjectImp is really necessary ? Not only it seems a waste,
it also makes it hard to implement application objects that inherit from
each other (the classname has to be passed as a param to the ctor, which
is really ugly ;) - or I need two ctors, one for inherited classes (with a classname
parameter) and one for direct construction (with the hardcoded name).

Shouldn't we store the classname in the ClassInfo ?

BTW I have started porting the ecma bindings, that's where I've seen
this problem.

David.

[prev in list] [next in list] [prev in thread] [next in thread]