() l...@gnu.org (Ludovic Courtès)
() Sun, 21 Apr 2013 21:04:23 +0200
https://gitorious.org/gnutls/gnutls/blobs/master/guile/tests/Makefile.am
Thanks for the link.
> If yes, does it give good results?
Well, yes. :-)
Cool. Let's see how that works for Guile-SDL.
--
Thien-Thi Nguyen
> When changing the _type_ of an argument this will perhaps not have the
> desired result. You have to consider the specific situation quite
> careful.
I'm aware of that. The CL hyperspec comes with the same warning.
I would probably only use it for initialize, where the next method
is basically
On 22 April 2013 01:17, Tobias Brandt wrote:
> I just noticed something: next-method *already* supports calling it with
> different arguments. It's just not documented.
>
When changing the _type_ of an argument this will perhaps not have the
desired result. You have to consider the specific situ
Thien-Thi Nguyen skribis:
> () l...@gnu.org (Ludovic Courtès)
> () Sat, 20 Apr 2013 16:04:49 +0200
>
>What about setting GUILE_AUTO_COMPILE=0 in ‘TESTS_ENVIRONMENT’ then?
>
>The ideal thing would be to build and install .go files. In that
>case, you would need to set ‘GUILE_COMPILED_
() l...@gnu.org (Ludovic Courtès)
() Sat, 20 Apr 2013 16:04:49 +0200
What about setting GUILE_AUTO_COMPILE=0 in ‘TESTS_ENVIRONMENT’ then?
The ideal thing would be to build and install .go files. In that
case, you would need to set ‘GUILE_COMPILED_LOAD_PATH’ appropriately
when running
I just noticed something: next-method *already* supports calling it with
different arguments. It's just not documented.
(define-class ())
(define-class ())
(define-method (f (self ) (x ))
(format #t "foo: ~a\n" x))
(define-method (f (self ) (x ))
(next-method self (1+ x)) ;; change ar
Hi,
thanks for your input. I tried to avoid the whole next-method issue
entirely and defined a method for make on bar's metaclass instead.
(use-modules (oop goops))
(define-class () (s #:init-keyword #:s))
(define-class ())
(define-class () #:metaclass )
(define-method (make (self ) (i ))
