i don't do that. i hack C into my assembly instead :)
On 7/10/08, Aaron Ardiri <[EMAIL PROTECTED]> wrote:
> On Wed, Jul 9, 2008 at 10:18 PM, Luc Le Blanc wrote:
> > Wow! That's too extreme for me. I link the Glue library anyway for various
> > other APIs, so I'll let the linker do its smart lin
On Wed, Jul 9, 2008 at 10:18 PM, Luc Le Blanc wrote:
> Wow! That's too extreme for me. I link the Glue library anyway for various
> other APIs, so I'll let the linker do its smart linking and only pick what's
> needed.
> And best reason to go no further: it works!
it was a suggestion if you got s
Welcome back Aaron!
You were very much missed.
I see your humor has stayed with you. :-)
Lionscribe
--
For information on using the ACCESS Developer Forums, or to unsubscribe, please
see http://www.access-company.com/developers/forums/
Aaron Ardiri wrote:
> why not create a very simple program that calls the
> LstGlueSetIncrementalSearch function; then you can diassemble
> it using a combination of par, and pilotdis
> (par e code 1; pilotdis code0001.bin)
> then, you'll get a file called code0001.bin.s - which, has
> the assemb
On Tue, Jul 8, 2008 at 2:06 PM, Luc Le Blanc <[EMAIL PROTECTED]> wrote:
> My first app segment contains a single C file that embeds all procs
> that must be in the first segment in order to be able to properly handle
> Global Find and beamed data when the app is not running (i.e.
> global-less mode
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 cal
in such case i think all you can do is reorder functions a bit
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
LstGlueSetIncre
My first app segment contains a single C file that embeds all procs that must
be in the first segment in order to be able to properly handle Global Find and
beamed data when the app is not running (i.e. global-less mode). Now, if I try
to link the Glue Library to this in order to have access to
