Jon Wilson <[EMAIL PROTECTED]> writes:
>
> But I can't find any way to get at that `name' property. Not that I
> need to, I'm just curious.
`procedure-name', which is separate from those object property bits.
> the phrase identifying it should be removed from the manual,
Thanks, I'll do that.
Jon Wilson <[EMAIL PROTECTED]> writes:
> Hi all,
> In the guile manual (at
> "http://www.gnu.org/software/guile/docs/guile-ref/Object-Properties.html#Object%20Properties";),
> in the second paragraph, we see
>
> "For example, all procedures have a `name' property, which stores
> the name of th
[EMAIL PROTECTED] (Han-Wen Nienhuys) writes:
>
> ## Remove fileblocks.o from the object list. This file gets added by
> ## the Autoconf macro AC_STRUCT_ST_BLOCKS. But there is no need.
> #LIBOBJS="`echo ${LIBOBJS} | sed 's/fileblocks\.o//g'`"
Actually, the bit preceding that seems relevant,
#
Hi all,
In the guile manual (at
"http://www.gnu.org/software/guile/docs/guile-ref/Object-Properties.html#Object%20Properties";),
in the second paragraph, we see
"For example, all procedures have a `name' property, which stores the
name of the variable in which the procedure was stored by a d
On 02-05, William Xu wrote:
> Yeah, i understand that. But i thought this ought to be done
> automatically in some way, not requiring user to do this manually, which
> would make codes less readable, isn't it?
(debug-set! stack 0)
would do the trick (disabling stack depth management) afaik?
--
In article <[EMAIL PROTECTED]>, Marius Vollmer <[EMAIL PROTECTED]> wrote:
>We are pleased to announce the release of Guile 1.7.91. This is a
>release candidate for Guile 1.8. It can be found here:
cross-compiling from Linux/x86 to Mingw/x86:
Making all in libguile
make[2]: Entering directory
