Quoting Bill Nottingham <[EMAIL PROTECTED]>:
In the NEWS file of guile-1.8.0:
....
** The GC can no longer be blocked.
The global flags scm_gc_heap_lock and scm_block_gc have been removed.
The GC can now run (partially) concurrently with other code and thus
blocking it is not well defined.
....
So, I'd read that as 'no'. (I'm in no way an expert on guile internals.)
Yeah, I'm not an expert, either. From reading that note I would suspect
that the reasons we tried to block the GC aren't /as/ relevent in 1.8..
So perhaps a guile-version-based compile-time flag would be appropriate.
I know at build-time if we've got 1.6 or 1.8, so we can just put those
blocks within #ifdef GUILE_BLOCK_GC and define /that/ based on a configure
test.
Bill
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
[EMAIL PROTECTED] PGP key available
_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
