All, This is a classic problem that we once encountered with hb_stack many time ago. I would suggest that to the most extent posible, third party developer should take note that direct access to internal structure should be avoided. Exactly as what we have now by discouraging the use of HB_API_MACROS/HB_STACK_MACROS.
I don't exactly know wheter we have APIs to manipulate PHB_DYNS. In case we don't, then we should provide ones. -- Andi On Thu, 27 Nov 2008 12:01:52 +0100 Miguel Angel Marchuet <[EMAIL PROTECTED]> wrote: > Message-ID: <[EMAIL PROTECTED]> > > Andi Jahja escribió: > > Miguel, > > > > Or we can temporarily provide old binary compatibility by changing: > > > >> #ifndef HB_NO_PROFILER > >> ULONG ulCalls; /* profiler support */ > >> ULONG ulTime; /* profiler support */ > >> ULONG ulRecurse; /* profiler support */ > >> #endif > > > > To: > > > > #if ( !defined( HB_NO_PROFILER ) || defined ( OLD_FWH_BINARY ) ) > > ULONG ulCalls; /* profiler support */ > > ULONG ulTime; /* profiler support */ > > ULONG ulRecurse; /* profiler support */ > > #endif > > > > So, those who do not want to recompile FWH/3rd party, should compile > > xHarbour with -DOLD_FWH_BINARY ...or whatever define constant you may > > call it. > > Better -HB_LEGACY_LEVEL instead of -DOLD_FWH_BINARY, similar use of it at > Harbour and other places to preserve compatibility > > > Do you agree ? > > Best regards, > Miguel Angel Marchuet ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ xHarbour-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xharbour-developers
