Re: Building the igc branch on MS-Windows

[Gerd Möllmann]

Po Lu <luangruo@yahoo.com> writes:

> It could easily be related to scroll bars, since the implementation of
> scroll bars on X liberally creates PVEC_OTHER objects that are subject
> to garbage collection.  No special handling is required of the GC,
> because the only objects after the Lisp area of the pseudovector are X
> identifiers and miscellaneous integers.

Ah thanks. Can we somehow distinguish this from other uses of
PVEC_OTHER?

> On another score, as I searched for other references to PVEC_OTHER, I
> did notice that there remains the other matter of module references,
> which probably needs to be revisited for this new GC scheme.  If the
> existing design is to be left intact, the PVEC_OTHERs created there must
> be "pinned" so that they are never moved by the garbage collector, but
> not having studied the igc branch beyond the superficials I cannot say
> how that is best accomplished.

I tackled that with my last commit. The remaining problem is to
distinguish the different uses of PVEC_OTHER (maybe a simple enum). On
macOS, the module stuff is the only use.