Hello again,
> Brandon Invergo writes:
>
>> I can try something like this:
>>
>> (let ((old-absolute-file-name? absolute-file-name?))
>> (define-generic absolute-file-name?)
>> (define-method (absolute-file-name? (f ))
>> (proper-list? (route f)))
>> (define-method (
Hi Brandon,
Brandon Invergo writes:
> I can try something like this:
>
> (let ((old-absolute-file-name? absolute-file-name?))
> (define-generic absolute-file-name?)
> (define-method (absolute-file-name? (f ))
> (proper-list? (route f)))
> (define-method (absolute-fi
Hi Mark or anyone else able to help,
Thanks again for raising this issue with my guile-file-names module:
Mark H Weaver writes:
> I see that you are using 'set!' to mutate several core bindings in the
> (guile) module to much slower GOOPS generic functions. For example, you
> 'set!' the core 'a
Hi Mark,
Mark H Weaver writes:
> Sorry, I meant to give an example of this. Please see srfi/srfi-45.scm
> in the Guile source distribution for an example of the preferred way to
> override core bindings, such that only modules that import your module
> are affected.
Thanks for the example. I w
Hi again,
I wrote:
> If you must override core procedures, then please use #:export and
> #:replace in the 'define-module' form, and simply 'define' the new
> binding in your module instead of using 'set!'. That way, the bindings
> in (guile) will be left unchanged, and your new bindings will onl
Hi Brandon,
Brandon Invergo writes:
> I'm happy to announce the release of guile-file-names 0.2.
>
> The (file-names) module provides methods for manipulating file names.
> Its design distinguishes between the human-friendly string format of
> filenames ("/usr/bin/guile") and a more Scheme-frien
Hello,
I'm happy to announce the release of guile-file-names 0.2.
The (file-names) module provides methods for manipulating file names.
Its design distinguishes between the human-friendly string format of
filenames ("/usr/bin/guile") and a more Scheme-friendly representation
to take out all the l
