my first guess is that the GOOPS method combinator accepts the
(. args) method and proceeds to do strange things instead of giving an
error message (as it should, because you introduce an ambiguity into
the dispatch).
anyway, here is a variant of your code that will work:
(use-modules (oop goo
Marius Vollmer <[EMAIL PROTECTED]> writes:
> Mikael Djurfeldt <[EMAIL PROTECTED]> writes:
>
> > Keisuke Nishida <[EMAIL PROTECTED]> writes:
> >
> > > The following code makes an error. Is this a feature or a bug?
> > >
> > > guile> (hash-fold acons () (make-vector 5))
> >
> > It's a bug in t
[EMAIL PROTECTED] writes:
> when running autogen.sh in guile-readline, you get the following
> error:
>
> aclocal: configure.in: 8: macro `AM_PROG_LIBTOOL' not found in library
>
> I imagine this leads to the configure problems later in the build.
check that you have at least Libtool 1.3
Ian Grant <[EMAIL PROTECTED]> writes:
> If I run
>
>gcc -E -DSCM_MAGIC_SNARFER readline.c
>
> in the guile-readline directory then I get just two lines:
>
> # 1 "readline.c"
>
> and
>
> # 525 "readline.c"
>
> separated by lots of blank lines.
what's your platform?
when did you la
Fabrice Tudoret <[EMAIL PROTECTED]> writes:
>cd /tmp/fabrice
>sh configure --prefix=/opt/local/guile --disable-shared
>
> the configure works a lot and stop with this message:
>checking for guile-config... no
>configure: error: Cannot find guile-config -- Install GUILE 1.3 and
>
"K Witt" <[EMAIL PROTECTED]> writes:
> [I apoligize for any oddities in this document -- I have doubts about this
> mail agent's reliability. Please put "TO JULIAN" or the like within
> the subject line of a reply.]
OK.
> My system is:
>Guile version 1.4.1
>Linux 2.2.14 on a Pentium pr
Dirk Herrmann <[EMAIL PROTECTED]> writes:
> On Thu, 6 Jul 2000, Han-Wen Nienhuys wrote:
>
> > why do assq-ref and friends return #f when the key is not found, in
> > stead of #? This makes it kind of hard to distinguish
> > between an alist not containing KEY and (KEY . #f)
>
> Actually, it wo
Dirk Herrmann <[EMAIL PROTECTED]> writes:
> [snip]
oops, the whole pagesize stuff slipped in by mistake, it's not even
needed.
will fix, thanks you.
--mike, for whom the thing did compile on Solaris. hmmm.
--
It is impossible to sharpen a pencil with a blunt axe. It is equally vain to
try
Martin Wilck <[EMAIL PROTECTED]> writes:
> I think there is a bug in the (ice-9 syncase) module.
does it help to use
(use-syntax (ice-9 syncase))
instead of
(use-modules (ice-9 syncase))
?
--
Roses are red,
Violets are blue,
I'm schizophrenic...
And I am too.
Keisuke Nishida <[EMAIL PROTECTED]> writes:
> It seems the current Guile does not do properly tail-call
> when a procedure is called through map.
I may be wrong, as I'm very out of practice wrt reading the Guile
evaluator code (ouch), but here is what happens:
`map' is implemented as a primitiv
Matthew R Wette <[EMAIL PROTECTED]> writes:
> One more piece of information. I gdb'd a core dump and
> it crashes at line 1407 in gc.c:
> m += free (vtable_data, (scm_bits_t *) SCM...
> Here the variable "free" is 0.
hrm. looks like scrambled bytes.
still, more information would be help
Matt Wette <[EMAIL PROTECTED]> writes:
> I did a "cvs update" on guile today.
> In guile-core I ran "autogen.sh" then "configure --prefix=/opt/guile"
> and then "make". The compile failed because of no "force". configure.in
> is adding "-dlpreopen force" to the load ...
what version of libtool
Matthias Koeppe <[EMAIL PROTECTED]> writes:
> [ ... poof! ...]
will commit, thank you!
[ it's very nice that somebody's testing Guile compiled with something
different from gcc. how does it run after you compiled it, btw? 64
bits, etc... ]
--
There are many intelligent species in the un
Dirk Herrmann <[EMAIL PROTECTED]> writes:
> Does the produced file "check-guile" get installed? (please forgive my
> autoconf/make ignorance). If so, is it possible to have it _not_
> installed? IMO, it is sufficient if "make check" works from the build
> directory after "make install" has bee
Martin Grabmueller <[EMAIL PROTECTED]> writes:
> The Guile - CVS page on savannah contains incorrect information about
> checking out CVS modules. It states that I have to do
>
> cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/guile co guile-core
>
> to check out guile-core, but that gives
>
> m
Gary Houston <[EMAIL PROTECTED]> writes:
> Probably not worth it at present: the current ptob system may need to
> be replaced with something more flexible, if such a thing can be
> devised.
you might find this interesting, now that GOOPS is integrated:
http://www.franz.com/support/documentatio
Neil Jerram <[EMAIL PROTECTED]> writes:
> [ should this move to guile-devel? ]
I CC'd there, at least.
> > "Martin" == Martin Grabmueller <[EMAIL PROTECTED]> writes:
>
> Martin> (1) We could change the build stuff to fire up Guile once,
> Martin> and snarf all .x and .doc files in
Bill Schottstaedt <[EMAIL PROTECTED]> writes:
> If I add this at line 567 in backtrace.c (just after the scm_make_print_state):
>
> scm_protect_object(print_state);
>
> the program works fine, but of course that isn't the "right thing".
it's quite close, actually.
I'll check in a fix shortly
Bill Schottstaedt <[EMAIL PROTECTED]> writes:
> I think there is an "scm_mallocated leak" in association with
> object->string.
oh. thanks for the report, I'll look at this later today.
[ the whole approach of making things signed so that (if you are
lucky) you can detect overflows stinks.
Masao Uebayashi <[EMAIL PROTECTED]> writes:
> I'm compiling a CVS tree just updated and get the following error.
>
> gcc -DHAVE_CONFIG_H -I.. -I./.. -I../libltdl -g -O2 -Wall -Wmissing-prototypes
>-Wp,-MD,.deps/gc.pp -c gc.c -fPIC -DPIC -o .libs/gc.o
> ../libguile/gc.x: In function `scm_init_g
Martin Grabmueller <[EMAIL PROTECTED]> writes:
> The problem is that I can not imagine a way to safely create unique
> symbols, since the only functions left for creating symbols are
>
> extern SCM scm_mem2symbol (const char*, scm_sizet);
> extern SCM scm_str2symbol (const char*);
>
> which
Marius Vollmer <[EMAIL PROTECTED]> writes:
> "Golubev I. N." <[EMAIL PROTECTED]> writes:
>
> > To allow guile work with native awk it needs at least one patch.
>
> We already have a fix for SCO nawk in CVS. Does it help?
might not, if the version of SCO is different, or something.
and I just
"Golubev I. N." <[EMAIL PROTECTED]> writes:
> > I would like it if they could be replaced with Guile programs, even
> > if that means a slightly more contorted build procedure.
>
> It is just another wording of what I wrote on Wed, 16 May 2001
> 13:30:44 in <[EMAIL PROTECTED]>. Why do not just
Boris Blankleider <[EMAIL PROTECTED]> writes:
> I have a problem building guile-1.4 on True64 V4.0f
> After ./configure, make gets stuck. The last output of the build is:
>
> mv -f .libs/debug.lo debug.o
> (cd . && ln -s debug.o debug.lo)
> PATH=.://bin:.:/sbin:/usr/sbin:/usr/bin:/usr/dt/bin:/us
"Dale P. Smith" <[EMAIL PROTECTED]> writes:
> Marius Vollmer wrote:
> >
> > "Dale P. Smith" <[EMAIL PROTECTED]> writes:
> >
> > > I just tried to compile cvs guile on a cobalt Qube 3 (intel, 2.2.x
> > > kernel, hacked over RedHat distro) from a "make dist" that I made on my
> > > Debian unstabl
"Dale P. Smith" <[EMAIL PROTECTED]> writes:
> guile> (help string)
> `string' is a primitive procedure in the (guile) module.
>
> - primitive: string. chrs
> - primitive: list->string chrs
> Return a newly allocated string composed of the arguments, CHRS.
> strings.c:103: wrong position f
26 matches
Mail list logo
