I found the cause of the bug, but more by happenstance than intent.I had attempted to do something clever during metaclass initialization -- attempting to ensure all class instantiations had a specific slot. I consed a new initargs parameter but failed to produce exactly what the base implementati
"Pat Lasswell" <[EMAIL PROTECTED]> writes:
> I have two questions. Is there something intrinsically wrong with with
> setting
> the current module to the one on which I am actively working and then just
> reloading that file rather than the entire suite?
No.
>
> My second question is this: gi
"Pat Lasswell" <[EMAIL PROTECTED]> writes:
>
> It seems that char 254 doesn't behave as expected in regular expressions on
> this platform.
Trying all bytes is probably bogus in a multibyte locale, but if we're
still in "C" locale at that point then it ought to work. (Maybe
should force (setlocal
The goops failures are a side effect of a change I made to (initialize ...) so that adding a method to no-applicable-method wouldn't crash; the warning arises from the generic function having one method instead of none after define-generic is called. There are details on bug-guile here:
http://li
Hi,
(Assuming we're talking about MacOS X on Intel-based macs. Maybe
`i386-apple-darwin*' is the correct GNU triple?)
"Pat Lasswell" <[EMAIL PROTECTED]> writes:
> make check produces 6 failures. I haven't tried 1.4, but 1.8 doesn't even
> build.
> FAIL: goops.test: defining generics: define-g
make check produces 6 failures. I haven't tried 1.4, but 1.8 doesn't even build.FAIL: goops.test: defining generics: define-generic: creating a new top-level bindingFAIL: goops.test: defining generics: define-generic: overwriting a top-level binding to a generic
FAIL: goops.test: defining accessor
Hi,
"Pat Lasswell" <[EMAIL PROTECTED]> writes:
> In guile 1.6.8 on an intel mac, I've encountered reliable heap corruption with
> steps like the following
Before investigating any further, does Guile 1.6.8 "works" on Intel
Macs? Is it under MacOS X? For instance, did you successfully run the
t
In guile 1.6.8 on an intel mac, I've encountered reliable heap corruption with steps like the following% guileguile> (use-modules (project all))guile> (set-current-module (resolve-module '(project foo)))
guile> (load "foo.scm")==> segmentation fault(project all) is a module that loads all of the pr
