Re: heads up: goops class export

Hi, On Sun 01 May 2011 22:32, Andy Wingo wi...@pobox.com writes: Currently when you define a SMOB type or set a name on a vtable, a corresponding class is automatically exported from (oop goops). This breaks modularity, and I think we should stop doing it in 2.2. I will make this change at

Re: heads up: goops class export

Hi! On Tue 03 May 2011 10:50, l...@gnu.org (Ludovic Courtès) writes: Andy Wingo wi...@pobox.com writes: Currently when you define a SMOB type or set a name on a vtable, a corresponding class is automatically exported from (oop goops). This breaks modularity, and I think we should stop

Re: heads up: goops class export

Hello! Andy Wingo wi...@pobox.com writes: On Tue 03 May 2011 10:50, l...@gnu.org (Ludovic Courtès) writes: Andy Wingo wi...@pobox.com writes: Currently when you define a SMOB type or set a name on a vtable, a corresponding class is automatically exported from (oop goops). This breaks

Re: heads up: goops class export

Hi :) On Tue 03 May 2011 14:19, l...@gnu.org (Ludovic Courtès) writes: Andy Wingo wi...@pobox.com writes: smob-name-class Yes, why not. (It’s equivalent to (@@ (oop goops) foobar) in terms of providing access to everyone, though.) OK. GOOPS really isn't for the ocap folks, given

heads up: goops class export

Hello again, Currently when you define a SMOB type or set a name on a vtable, a corresponding class is automatically exported from (oop goops). This breaks modularity, and I think we should stop doing it in 2.2. I will make this change at some point, if there are no objections. Andy --