Michal Seliga wrote:
> in such case i think all you can do is reorder functions a bit
Been there, but I now hit the domino efect if I move anything :(
> or with switched optimizations you can make sequentional jumps to
> glue library (from place where you need
> LstGlueSetIncrementalSearch call small not inlineable function
> placed somewhere in the middle which will call
> LstGlueSetIncrementalSearch which will be linked after your main
> c file)
This is smart! (and so simple!)
I just added :
#pragma dont_inline on
void LstSetIncrementalSearch( ListPtr list, Boolean enable )
{
LstGlueSetIncrementalSearch( list, enable );
}
#pragma dont_inline reset
at about half of my C file, and things work fine. Thanks!
Luc Le Blanc
--
For information on using the ACCESS Developer Forums, or to unsubscribe, please
see http://www.access-company.com/developers/forums/
