Re: g-wrap: guile-CVS build error

[Andreas Rottmann]

Jan Nieuwenhuizen <address@hidden> writes:

> Jan Nieuwenhuizen writes:
>
>> (if (defined? 'class-name)
>>     (define class-name (ensure-accessor class-name))
>>     (let* ((oop-goops (resolve-module '(oop goops)))
>>         (goops-class-name (module-ref oop-goops 'class-name)))
>>       (define class-name (ensure-accessor goops-class-name))))
>>
>> But that doesn't work?
>
> (if (defined? 'class-name)
>     (define class-name (ensure-accessor class-name))
>     (define class-name (ensure-accessor (module-ref
>                                        (resolve-module '(oop goops))
>                                        'class-name))))
>                                          
> Ah, this works, but compiling guile-gnome with GUILE CVS, there are
> lots of warnings.  I Realize that this may be the cause of my recent
> LilyPond problems with guile-1.6: (oop goops) gets imported, and
> lateron gwrap also imports (oop goops), but with some stuff altered
> (like class-name?)
>
Yes, you have to import (oop goops) before (g-wrap). This issue will
vanish with 1.9.1, where I've renamed class-name to
name-of-class. Since 1.9.1 will have many backwards-incompatible
changes, I've created a branch for stuff that should go in 1.9.0:
g-wrap--mainline--1.9.0. Could you "tla join-branch" that and then
commit? Otherwise trying to star-merge your branch into
mainline--1.9.0 fails with "unable to merge unrelated trees".

Andy
-- 
Andreas Rottmann         | address@hidden      | address@hidden | address@hidden
http://yi.org/rotty      | GnuPG Key: http://yi.org/rotty/gpg.asc
Fingerprint              | DFB4 4EB4 78A4 5EEE 6219  F228 F92F CFC5 01FD 5B62

The best way to accelerate a Windows machine is at 9.81 m/s^2