Hi again,
and, to be very very precise, I even renamed my directory now [which appears in
the
compilation trace] because its previous name was terrible (and terribly wrong)!
so, the appropriate directory name is: .../setter-inheritance-bug
[ the new trace is here below, 'in place'
Hello Andy,
we should change the subject or start a new thread, maybe
> Are you certain? What git revision are you using? I don't think the
> test should "work" with the current stable-2.0 or master, or 1.8 for
> that matter.
Oh no, it's not working as it should, too bad: this time I
On Tue 27 Jan 2015 20:11, David Pirotte writes:
>> The setters inheritance bug is fixed to be like 1.8.
>
> Thanks, it _does_ work as expected now, now as in using the latest
> stable-2.0!
Are you certain? What git revision are you using? I don't think the
test should "work" with the current s
To be complete, raise the confusion, and allow who would want to follow and
test, the setter bug test case I pasted on irc was this one (*):
Using guile versions previous to the goops refactoring work Andy did recently,
you'd
have this answer:
scheme@(guile-user)> ,use (oop goops)
Hello Andy,
- we should not have mixed the 'accessor' problem as reported by
another user and the setter bug I reported [on irc];
- also I should have reported a separate bug to bug-gu...@gnu.org, but I
thought we perfectly understood each other, I was wrong and we
On Tue 27 Jan 2015 02:00, David Pirotte writes:
>> Can you make a test case without guile-gnome?
>
> No, it is a guile-gnome problem/bug, so here below, a very short test case (*)
OK, then please file it in the guile-gnome bugzilla. Thanks. We
probably don't need to talk about it on guile-dev
