Geir,
Took sometime to get back at this (an interesting movie on TV).
Ok, there is a single point for introspection call which is from:
ASTIdentifier.doIntrospection( Class data )
Now, having:
public interface IntrospectionBuilder
{ public AbstractExecutor doIntrospection( String identifier, Class data )
throws Exception;
}
and an extra field for the Parser class like:
public final IntrospectionBuilder introBuilder;
one could replace the introspection call (in ASTIdentifier.execute()):
executor = doIntrospection( c );
by
parser.introBuilder.doIntrospection( identifier, c );
Profits:
The possibility of having plugable introspection, even per Parser.
Costs:
- An extra member, and its initialization, for the Parser class. Since
a pool of such objects is used, this is a very low cost.
- A couple of extra references and an extra parameter to create the
introspection. This is not such high cost either.
Well, actually, maybe this costs less than keeping and initializing that
"method" field (in the ASTIdentifier class) that is not being used any
more.
=;o)
What do you think about this?
Paulo
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Geir
> Magnusson Jr.
>
> Before we consider that, does the above solve your problems?
> Pluggable discovery sounds slow, and Vel isn't going anywhere big
> unless we get to JSP-like performance.
>
> geir
