db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-739) Reduce generated code required to access a parameter's value
Date Thu, 01 Dec 2005 20:46:35 GMT
Reduce generated code required to access a parameter's value

         Key: DERBY-739
         URL: http://issues.apache.org/jira/browse/DERBY-739
     Project: Derby
        Type: Sub-task
    Reporter: Daniel John Debrunner
    Priority: Minor

When accessing a parameter the generated code is:


A slightly shorter form would be


if a getParameter() method was added to BaseActivation that simply did:
 protected final DataValueDescriptor getParameter(int n) { return pvs.getParameter(n); }

An interesting separate idea, to reduce the number of constant pool entries would be to have
multiple getParameter() methods, that took values from 0-5 to construct the actual parameter

getParameter(3) -- >  3 parameter (0 based)
getParameter(2, 1) --> 13 parameter (2*6 + 1)
getParameter(5, 1, 4) --> 190 parameter (5*36 + 1*6+ 4)
above the limit of three args, revert to getParameter(n)

This should probably be a separate issue and probably would increease code size which would
not help DERBY-732 , it's a tradeoff between constant pool entries and code size.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message