Recently I posted some questions concerning problems with 16 bit sets.
I got good suggestions from some of you, but further analysis of the
code revealed this kind of construct:
****************************
TYPE
    INT16        =    INTEGER(16);
    INT8         =    packed 0..
    INT0_65535   =    packed 0..65535;
    B_TYPE       =   (B1, B2, B3, B4, B5, B6, B7, B8);
    BITS         =   (BIT0,BIT1,BIT2,BIT3,BIT4,BIT5,BIT6,BIT7,BIT8,BIT9,
                      BIT10,BIT11,BIT12,BIT13,BIT14,BIT15);
    B_TYPE_SET   =    set of B_TYPE;
    BIT_SET      =    set of BITS;

VAR
    OUT_REC      =    record case INT16 of
                        0 :  (BSLB: B_TYPE_SET;
                              BSHB: B_TYPE_SET);
                        1 :  (USRINT : INT0_65535);
                        2 :  (BT: BIT_SET);
                      END;

******************************
The code heavily depends on the record variants to be aligned exactly on top of each
other.

Is there anyone in the GPC project that is working, or planning to work,
on this issue?
("optimized set constructor"??)
How long would it take?
The company I'm working for, HiQ Approve AB, is willing to discuss a
financial contribution to get this done.

Best Regards

Sven Jauring