Mike Gran <[EMAIL PROTECTED]> writes:
>
> I wrote a peer-to-peer ap where I used "(display data socket)" to send
> and "(read-string!/partial block socket-port)" to receive.
That'd be the ticket, I use a `socketpair' and read-string to talk back
and forward to a child process. You have to have
Kaloian Doganov <[EMAIL PROTECTED]> writes:
>
> I need to do record (range) locking, not whole-file locking, and I
> hoped to do it with Guile.
If you don't mind breaking out a little C code it shouldn't be too hard.
(I can never remember which types of locks are voluntary or mandatory,
and which
Roland Orre <[EMAIL PROTECTED]> writes:
>
>> What is the best way to limit the memory allocation in guile?
Perhaps setrlimit would be the most reliable overall.
>> I'm still running 1.7 as I haven't got the time and energy
>> to change the array implementation yet.
I struck a bug lately in 1.8 w
Kaloian Doganov <[EMAIL PROTECTED]> writes:
>
> Neighter F_GETLK nor F_SETLK is there.
Yep, not there. It'd need something for "struct flock" (and "struct
flock64" when available), they're not plain integers like the other
fcntl commands.
There's `flock' already for whole-file, if that's enough.
Daniel Ridge <[EMAIL PROTECTED]> writes:
>
> SCM_DEFINE(guile_srcprops_p, "srcprops?", 1, 0, 0,
I don't think that's meant to be visible, merely a compact form of
what's normally prsented as an alist. If you want a test then one
possibility would be that it automagically shows up in goops as a
`'
Andy Wingo <[EMAIL PROTECTED]> writes:
>
> (1) garbage collection requires cooperation between threads; if the main
> thread running gtk-main doesn't check in now and then the app will lock
> up in gc
The old guile-gtk has a set of GThreadFunctions that still work in
1.6, if you wanted to compare
"Alex Gittens" <[EMAIL PROTECTED]> writes:
>
> guile> (probably-prime? 13)
> : In expression (probably-prime? 13):
> : Unbound variable: probably-prime?
Is it called `prime?' rather than `probably-prime?' ?
___
Guile-user mailing list
Guile-user@gnu.or
[EMAIL PROTECTED] (clemens fischer) writes:
>
> i just checked "guile-1.8.1/libguile/stime.c", which doesn't have this
> patch,
I applied Aaron VanDevender's prior one.
> $ guile -c '(display (strftime "%c %z\n" (localtime (current-time'
> Mon Jan 29 19:31:28 2007 -0100
I believe it's in
Hugh Sasse <[EMAIL PROTECTED]> writes:
>
> I didn't invoke automake myself, I was just disclosing the toolset.
> Does it get fired off by autoreconf?
It provides some of the macros used in generating the configure
script.
___
Guile-user mailing list
Gu
Ales Hvezda <[EMAIL PROTECTED]> writes:
>
> Is this expected and/or intentional behavior?
Thanks, it's a bug. I'll apply a fix.
___
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
Hugh Sasse <[EMAIL PROTECTED]> writes:
>
> automake (GNU automake) 1.9.6
You might have to check where it's .m4 macros are installed. If
they're not in a known place you can run
aclocal -I /my/automake/dir/share/aclocal
or wherever.
You might not have to run aclocal, but I've never kno
Hugh Sasse <[EMAIL PROTECTED]> writes:
>
> mov 0, %o1
> callprintf, 0
Ah dear, thanks, gcc has optimized it out. I'll change the test
program to something like
#include
volatile double x = 0.0;
int main () { return (isinf(x) != 0); }
probably add
Hugh Sasse <[EMAIL PROTECTED]> writes:
>
> I'm stumped. And sun's native patch implementation chokes on this.
Should have been ok. Change the lines manually, or checkout the cvs
"branch_release-1-8" if you're brave.
___
Guile-user mailing list
Guile-
William Xu <[EMAIL PROTECTED]> writes:
>
> Currently it just makes me feel uncomfortable when it doesn't work as
> expected.. I hope someday it could get fixed.
I'll add something like the following to the manual for a start, to at
least describe how it works now ...
Scheme code signal ha
Hugh Sasse <[EMAIL PROTECTED]> writes:
>
>> You might be able to stick something in to save the conftest.c used.
>
> Possibly. I'm not familiar enough with autoconf to be confident about
> that.
Oh, what I meant was if you edit the generated configure to do a cp of
conftest.c at the right spot.
I made this change:
--- configure.in.~1.268.2.28.~ 2006-12-27 10:32:04.0 +1100
+++ configure.in 2007-01-22 10:03:13.0 +1100
@@ -27,8 +27,15 @@
AC_PREREQ(2.53)
-AC_INIT(m4_esyscmd(. ./GUILE-VERSION && echo -n ${PACKAGE}),
-m4_esyscmd(. ./GUILE-VERSION && echo -n ${GUILE
Hugh Sasse <[EMAIL PROTECTED]> writes:
>
> -AC_INIT(m4_esyscmd(. ./GUILE-VERSION && echo -n ${PACKAGE}),
> -m4_esyscmd(. ./GUILE-VERSION && echo -n ${GUILE_VERSION}))
> +define(GUILE_PACKAGE_NAME,m4_esyscmd(. ./GUILE-VERSION && ${ECHO_N}
> ${PACKAGE}))
> +define(GUILE_PACKAGE_VERSION,m4_es
Hugh Sasse <[EMAIL PROTECTED]> writes:
>
> ./.libs/libguile.so: undefined reference to `isinf'
>
> At which point I am now stuck. After all, configure found isinf.
You might be able to stick something in to save the conftest.c used.
Or maybe it's no more than
#include
int main (
William Xu <[EMAIL PROTECTED]> writes:
>
> So all other things are blocked during accept()?
Signals for the thread in question at least :(.
> Maybe this is a problem of scheme accept?
It's not a good thing, though fixing it might be tricky.
Do you actually need to know immediately the child exi
Hugh Sasse <[EMAIL PROTECTED]> writes:
>
> putenv putenv (3c) - change or add value to environment
>
> The manual page says it should be of the form "name=value" and the
> string should not be automatic. In a function it should be declared
> static.
Yep. I believe there's a bit of va
Hugh Sasse <[EMAIL PROTECTED]> writes:
>
> That rather depends on for whom they are developing. Aguments in
> "Brave Gnu World" about software use in the third world where download
> speeds are still limited,
Yep, such as Australia. The theory as I see it though is that there's
barely a dozen d
William Xu <[EMAIL PROTECTED]> writes:
>
> i wrote a simple echo server/client. To catch SIGCHLD signal, i install
> a signal handler before first `connect'. The problem is that when the
> client exits, the handler seems not called.
I expect you've checked with "ps" that the child has actually exi
Hugh Sasse <[EMAIL PROTECTED]> writes:
>
> posix.c: In function 'scm_putenv':
> posix.c:1332: error: 'len' undeclared (first use in this function)
Thanks. Dodgy conditionals :-(. You can use the "len" at the start
of the function (claiming to be for mingw).
Does that mean there's no unsetenv()
Hugh Sasse <[EMAIL PROTECTED]> writes:
>
> On Sat, 13 Jan 2007, Kevin Ryde wrote:
>
>> Otherwise if you think there's a function but no prototype we could
>> put a prototype in (when not otherwise provided).
>
> that sounds like the best approach to me. Th
Hugh Sasse <[EMAIL PROTECTED]> writes:
>
>> cc1: warnings being treated as errors
That's designed to force all users to be developers :-(.
>> numbers.c: In function 'xisinf':
>> numbers.c:147: warning: implicit declaration of function 'isinf'
You might be able to just stick in a prototype, or al
Neil Jerram <[EMAIL PROTECTED]> writes:
>
> In the meantime, can we fix this for guile by just adding #ifndef
> alloca around the whole blob? Would that have bad effects on other
> OSs?
Sounds good.
___
Guile-user mailing list
Guile-user@gnu.org
http:
[EMAIL PROTECTED] (Ludovic Courtès) writes:
>
> https://gna.org/projects/gee
>
> I don't know how it compares to Kevin's.
Integrated into an encode/decode framework, just from nosing around.
Incidentally, when I compared libiconv and librecode I thought recode
had the odd extra charset and mayb
Stan Pinte <[EMAIL PROTECTED]> writes:
>
> http://aruiz.typepad.com/siliconisland/2006/04/threads_on_pygt.html
I suppose a dynamic-wind for the enter/leave would ensure a "leave" if
there was an error in the protected section.
> My problem is that I cannot find anywhere a guile module containing
)
/* Chart miscellaneous C code.
Copyright 2003, 2005, 2006 Kevin Ryde
This file is part of Chart.
Chart is free software; you can redistribute it and/or modify it under
the terms of the GNU General Public License as published by the Free
Software Foundation; either version 2, or
Jon Wilson <[EMAIL PROTECTED]> writes:
>
> I need some help understanding what you've said.
AC_FUNC_ALLOCA in configure normally uses an alloca.c
(libguile/alloca.c) to provide alloca() if the compiler or C library
doesn't otherwise have one. Should be unrelated to whatever happens
on bsd.
Not s
[EMAIL PROTECTED] writes:
>
> It looks like the iota function from ice-9/boot-9.scm is called.
It took a while, but I made a fix for the next release.
___
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
Jon Wilson <[EMAIL PROTECTED]> writes:
>
> scmconfig.h seems to only be created while make all is running (try
> make scmconfig after ../configure).
Yes, it's generated.
> However, on my system, and Gopi's
> FreeBSD system as well, scmconfig.h includes . So,
> indirectly, eval.c includes , and d
Neil Jerram <[EMAIL PROTECTED]> writes:
>
> Yes from me; it sounds interesting and useful.
Me too.
Stringbufs have room for another flag that could say they're mmaps
(and hence should free with munmap).
I suppose a string is only good while strings are uninterpreted
8-bits. When they're some en
Jon Wilson <[EMAIL PROTECTED]> writes:
>
> Perhaps the definitions of alloca in eval.c should be wrapped in an
> "#ifndef alloca"?
Quite possibly. The blob used is from autoconf, so we can pass the
buck if it doesn't work :-).
___
Guile-user mailing l
Jon Wilson <[EMAIL PROTECTED]> writes:
>
> $ chmod a+x /path/to/guile-config
Which is supposed to be done by guile-config/Makefile.am at install
time of course. If that didn't happen maybe there's some bug ...
___
Guile-user mailing list
Guile-user@gn
[EMAIL PROTECTED] writes:
>
>> rlwrap guile181 --use-srfi=1
> guile> (iota 3 1)
>
> Backtrace:
> In standard input:
>1: 0* [iota 3 1]
>
> standard input:1:1: In procedure iota in expression (iota 3 1):
> standard input:1:1: Wrong number of arguments to #
> ABORT: (wrong-number-of-args)
> guile>
Neil Jerram <[EMAIL PROTECTED]> writes:
>
> Good point. I believe Jon's going to raise this (inability to do
> readline starting from the column after the prompt) with the readline
> people.
I see there's an rl_already_prompted, though you still have to tell it
the prompt string to make redisplay
This is what I ended up checking-in.
6.5.3 Readline Functions
The following functions are provided by
(use-modules (ice-9 readline))
There are two ways to use readline from Scheme code, either make
calls to `readline' directly to get line by line input, or use
Daniel Llorens del Río <[EMAIL PROTECTED]> writes:
>
> Absolutely, that's what I mean. Actually, maybe I'd prefer up-arrow to
> show
>
> guile> (define (foo)
> ... (bar))
>
> just as I would have typed it. But that's a minor detail.
I suspect readline can't display like that.
> The idea is, I g
I wrote:
>
> ... some words for the manual.
What else should be described?
Extra options to `readline' for the input/output ports, or is that
only meant for the %readline level and only set-readline-input-port!
for the high level?
(readline-port) create/return the readline port?
Is it possible
Neil Jerram <[EMAIL PROTECTED]> writes:
>
> + (let ((outer-new-input-prompt new-input-prompt)
> + (outer-continuation-prompt continuation-prompt)
Could there be a way for an application to get the prompts back,
so it could do the same sort of save/restore too?
_
Neil Jerram <[EMAIL PROTECTED]> writes:
>
> Slightly confusingly, set-readline-prompt! does also set the default
> prompt for an explicit `readline' call (1). I think the overall
> situation would be clearer if it didn't.
It's not too terrible, may as well leave it alone in case anyone's
nutted i
Neil Jerram <[EMAIL PROTECTED]> writes:
>
> ... instead of by a parameter to `readline',
Is that readline function meant to be used? I assume it's emulating
the C function of that name. If you use it and no other input it
works does it?
___
Guile-use
Jon Wilson <[EMAIL PROTECTED]> writes:
>
> This prints "prompt: " on a line, and then after a short time, it is
> erased.
It might be as simple as
(readline "foo: ")
Not sure if that's meant to be documented, seems like a pretty
sensible usage, even if reading current-input-port might be
"Pat Lasswell" <[EMAIL PROTECTED]> writes:
>
> Then, I have to edit the emitted config.h to remove
>
> #define socklen_t int
>
> because configure wrongly concludes it is absent from the system headers.
> It is also the cause of the warning during configure.
Thanks, I think we've got a fix for tha
"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
"Marco Maggi" <[EMAIL PROTECTED]> writes:
>
> Is it possible to have an ATEXIT function? That is:
> an interface to register thunks that are executed
> when the script exits.
I've been using this:
(define-public (c-atexit proc)
(let ((old-exit exit))
(set! exit (lamb
[EMAIL PROTECTED] (Ludovic Courtès) writes:
>
>(let ((errno (car (cadddr args ;; !!!
system-error-errno helps there. I made a few similar extracting funcs
at one time ... then found it better not to try to be too smart about
analysing errors!
> (guard (c ((i/o-no-such-file-error? c
Frank Middleton <[EMAIL PROTECTED]> writes:
>
> 1) Does anyone have any suggestions/opinions about the right
> way of getting past this?
There's some solaris fixes in the cvs, you might like to try that (or
a nightly snapshot).
___
Guile-user mailing
Daniel Llorens del Río <[EMAIL PROTECTED]> writes:
>
> Myself, I'd be happy if only things like this didn't happen:
>
> guile> (tanh 1e3+i)
> +nan.0
Perhaps the libc ctanh() etc could be used when available ... let
somebody else worry about overflows.
Jon Wilson <[EMAIL PROTECTED]> writes:
>
> There seem to be a number of repl related procedures that are
> exported. Should all of them be available?
Probably not. There's a fair bit of stuff in boot-9 that ought to
either made private or documented.
Andreas Røsdal <[EMAIL PROTECTED]> writes:
>
> When the cards get dragged the list of cards is kept purely on the C side
> of the code - hence there is an opportunity for them to get garbage
> collected.
Do you mean the CallData bits of cscmi_drag_valid and friends in
cscmi.c? Yes, they look a
Neil Jerram <[EMAIL PROTECTED]> writes:
>
> And if you're not keen on parsing arity's output, see its definition
> in (ice-9 session) for the procedure properties that it queries to
> produce this.
(procedure-property obj 'arity) being the operative part, it gives a
list of "(required-count option
Jon Wilson <[EMAIL PROTECTED]> writes:
>
> scm_c_primitive_load ... scm_c_eval_string
Thanks, I added them.
___
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
Per Bothner <[EMAIL PROTECTED]> writes:
>
>> | From: Marius Vollmer <[EMAIL PROTECTED]>
>> | Specifically, 'eqv?' would be changed to return '#t' when comparing
>> | negative and positive zero:
>> |
>> | (eqv? 0.0 -0.0) => #t
>
> I missed the explanation for why this might be desirable.
P
"Dave Griffiths" <[EMAIL PROTECTED]> writes:
>
> I tried running the example through the C preprocessor, and it seems
> the docstring is lost anyway:
There's some magic with a "-DSCM_MAGIC_SNARF_DOCS" to get them, then
the scripts/snarf-check-and-output-texi program picks them out from
the code.
"m.vaessen" <[EMAIL PROTECTED]> writes:
>
> libtool: link: not configured to extract global symbols from
> dlpreopened files
You might get a better answer on the libtool list for what that means.
> xlc_r -q64 -o .libs/guile -D_THREAD_SAFE guile-guile.o
> -L/usr/local/lib -L./.libs -lguile -lpthre
Aaron VanDevender <[EMAIL PROTECTED]> writes:
>
> +# GUILE_CHECK_VERSION -- check for a particular Guile version
> +#
> +# Usage: GUILE_CHECK_VERSION(MIN-VERSION, [ACTION-IF-FOUND],
> [ACTION-IF-NOTFOUND])
The autoconf philosophy is usually not to check version numbers
explicitly if it can be avo
[EMAIL PROTECTED] (Ludovic Courtès) writes:
>
> What was the reason to not have `list-equal?'? Was it the fact that we
> want it to be inlined within `equal?'?
You should hide it please. I think different equality test funcs are
generally exposed only when they do something different from plain
Charles Gagnon <[EMAIL PROTECTED]> writes:
>
> struct dirent ent;
> SCM_SYSCALL (readdir_r ((DIR *) SCM_CELL_WORD_1 (port), &ent));
I'm not sure that'll work, struct dirent can be small, hence the union
with the bigger amounts. If you're using that function you might be
better just puttin
[EMAIL PROTECTED] (Ludovic Courtès) writes:
>
> According to R5RS, if the two `chbouib' instances print equally, they
> should be `equal?'.
I don't think that's meant to be taken literally, I'm pretty sure what
it's only trying to say is that `equal?' recurses into containers like
lists and vector
stephane chatigny <[EMAIL PROTECTED]> writes:
>
> Does a Unix command like "pmap PID" could help me to determine if there
> is a memory leak in the process?
I suppose. I only ever look at "top" to see if it's going up.
___
Guile-user mailing list
Guil
Stephane Chatigny <[EMAIL PROTECTED]> writes:
>
> (although I have not tracked the memory usage yet).
You'll probably have to use one of the various malloc debugging
packages to find who has allocated the memory that's never freed, to
see who's supposed to be responsible for that.
__
Dan McMahill <[EMAIL PROTECTED]> writes:
>
> SCM scm_myfn(SCM flags)
> {
> myfn (scm_num2int (flags, SCM_ARG1, "myfn"));
Various things in the guile core are done like that, stuff like O_RDWR
for `open'. The list of symbols Ludovic described is done in the
guile-gtk interface and works nicely t
Dan McMahill <[EMAIL PROTECTED]> writes:
>
> ERROR: In procedure write_all:
> ERROR: Broken pipe
Yes, that's right, you get a scheme-level error instead of sigpipe
terminating the whole process. (See `catch' in the guile manual for
trapping that error, or perhaps false-if-exception to ignore it.)
Dan McMahill <[EMAIL PROTECTED]> writes:
>
> So is there an easy way to detect when the pipe was terminated so I
> can avoid crashing?
You can set the SIGPIPE signal to avoid terminating on a broken pipe.
Usually setting it to SIG_IGN is the cleanest, with that a write
throws an EPIPE error. (Rea
William Xu <[EMAIL PROTECTED]> writes:
>
> the original guile> prompt is gone
I think it's just been printed over on the tty. Try typing something,
it should be still there :-).
___
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailm
Mike Gran <[EMAIL PROTECTED]> writes:
>
> The 1.8 ref manual (sec 2.5) still says bug-guile@gnu.org is the way to
> report bugs. But, http://savannah.gnu.org/bugs/?group=guile exists,
> too.
>
> Is one of those two a preferred method?
Savannah relays to bug-guile. bug-guile is generally better b
Aaron VanDevender <[EMAIL PROTECTED]> writes:
>
> (section 2.3.4 refers to
> http://www.gnu.org/software/guile/docs/docs-1.8/libtool/index.html#Top)
I'll try to mung those links at some stage.
> But this documentation doesn't actually exist. Does anyone have even a
> sketchy HOWTO or a simple exa
William Xu <[EMAIL PROTECTED]> writes:
>
> i have already tried that..
Oh, I see, in 1.6 it's a bare recv() call, it doesn't cooperate with
the multi-threading. Hmm. Not sure if it's easy to fix that, it
works in 1.8 because pthreads takes care of all blocking.
As a workaround in 1.6 I think yo
Torsten Bronger <[EMAIL PROTECTED]> writes:
>
> 1) Will the result from scm_from_locale_string() garbage-collected
>cleanly?
Yep.
>My concern is that the program should be able to read from stdin,
>too, and I question the protability of the file name
>"/dev/stdin".
scm_current_in
"Marco Maggi" <[EMAIL PROTECTED]> writes:
>
> is there a sample extension implementing an input/output
> channel?
You'll have seen the "Soft Ports" node in the manual, it's pretty
straightforward.
> I'm thinking of a memory channel (not an interface
> to a file or hardware port), something like t
Jon Wilson <[EMAIL PROTECTED]> writes:
>
> Everything in this email still applies to 1.6, however.
Alas the 1.6 manual hasn't been getting updates, not beyond the level
of fixing outright errors.
> I actually intended to mean that the gh_ to scm_ section was not a
> very complete documentation of
Jon Wilson <[EMAIL PROTECTED]> writes:
>
> but all I've found is the section on trasitioning from gh_ to scm_,
> which isn't very complete.
What gh funcs are missing for instance?
> and not found several of the scm_ functions which are mentioned in
> the gh_ to scm_ transition page.
Such as? It
William Xu <[EMAIL PROTECTED]> writes:
>
> I have attached a reproducible testcase,
It works ok for me, unfortunately (on i386 with gcc 2.95).
___
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
Neil Jerram <[EMAIL PROTECTED]> writes:
>
> (define-macro (whatever ...)
> `(,what* ...))
That'd be the idea, works nicely with procedures, but I had trouble
unquoting macros/syntax bits. In the new guile 1.8 `while' in
boot-9.scm unquoting the `do' made (ice-9 syncase) very upset.
__
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.
[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,
#
Christian Mauduit <[EMAIL PROTECTED]> writes:
>
> (_ "my string")
Gettext can understand that directly, actually. With a recent version
it's something like
xgettext --language=scheme --keyword=_
With older gettext I think language=lisp works. xgettext recognises
`gettext' calls directl
William Xu <[EMAIL PROTECTED]> writes:
>
> Does guile support charset conversion? e.g., Display a string using
> my-charset coding system,
The short answer is no. Strings are just byte sequences, which is ok
if your input and output codings are the same, but needs an add-on if
you have to convert
William Xu <[EMAIL PROTECTED]> writes:
>
> any way to look into or trace, uniform-array-read! ?
If you put it under gdb you should be able to ^C when it's hung and
find out where it is. There's won't be much info except the function
names, unless you build a guile with "CFLAGS=-g".
Otherwise pos
Greg Troxel <[EMAIL PROTECTED]> writes:
>
> I tend to build program foo (from CVS) into /usr/foo.
I like that too except usually a subdir of wherever I keep the source.
Nice and easy to rm -r when you're sick of it. But I presume you, as
I, don't want a package build trying to modify /etc/profile
[EMAIL PROTECTED] (Ludovic Courtès) writes:
>
> (i) a config file holding the default value of `%load-path',
If you really want to add something, just load an /etc/guilerc at
startup. That'd be all the flexibility and wouldn't force add-on
modules to jump through hoops (not until the hoops are mu
Neil Jerram <[EMAIL PROTECTED]> writes:
>
> The basic scenario is this: someone has Guile installed (probably by
> their distro) in /usr, and then builds and installs an additional
> package using ./configure && make && sudo make install, which installs
> with a different prefix than /usr (usually
Andy Wingo <[EMAIL PROTECTED]> writes:
>
> A question though. What is the problem which is being solved here?
That's escaped me too.
(I have a feeling the present "site" dir is modelled on emacs, I
haven't been able to follow why it's not enough ...)
[EMAIL PROTECTED] (Ludovic Courtès) writes:
>
> Libtool's `.la' files are only used at compile-time, in order to
> find out library dependencies,
They're also read at runtime for dlopens (see ltdl.c try_dlopen) to
get depencency info (for the benefit of non-ELF systems I think).
"Rients van Wijngaarden" <[EMAIL PROTECTED]> writes:
>
> so obviously, scm_guard needs a third argument of type int, but my
> question is:
> What is this int?
Hmm. A flag saying whether you want an error thrown if the object is
already guarded.
Apparently scm_guard is going to be deprecated in t
Jon Wilson <[EMAIL PROTECTED]> writes:
>
> which seems to suggest (incorrectly, obviously) that the arguments to
> both assoc and assoc-ref should be the same. Perhaps, given that it
> seems that a fairly large number of people have misread the manual and
> gotten confused about this, it would be
Greg Troxel <[EMAIL PROTECTED]> writes:
>
> You are right, but if you object to going from what we have to what I
> posted, I don't see your point.
I was hoping the issue could be killed for good, ie. impervious to
anything guile.init might do in the future :-).
> slib needs to define the API tha
Neil Jerram <[EMAIL PROTECTED]> writes:
>
> In practice I would guess not. Most distribution-managed packages
> would go into /usr/share/guile, and most home-built packages into
> /usr/local/share/guile, I'd guess. What is your concern, though?
Mainly that I think you can get what you want from
Greg Troxel <[EMAIL PROTECTED]> writes:
>
> (define-module (ice-9 slib)
> :export (slib:load
> implementation-vicinity
> library-vicinity
> home-vicinity
> scheme-implementation-type
> scheme-implementation-version
I would worry very much that these a
Greg Troxel <[EMAIL PROTECTED]> writes:
>
> If all modules inherit from guile-user, then that sounds right. But
> this would expose slib's require machinery to all guile programs, even
> those that haven't asked for it, and that's not good.
I'm unsure if it would work any other way (ie. non-globa
Neil Jerram <[EMAIL PROTECTED]> writes:
>
> In the init.d approach, there would be a directory named
> $sysconfdir/guile/X.Y/init.d, and we would distribute an init.scm file
> (which Guile normally loads on startup) which would load all the files
> in $sysconfdir/guile/X.Y/init.d. So, for example,
Greg Troxel <[EMAIL PROTECTED]> writes:
>
> Whether there is something deeper with gnucash, I don't know, but I
> have no reason to think so yet.
I wondered if perhaps ice-9 slib was supposed to be like a proper
module, giving an slib environment only in those application modules
using it, and not
[EMAIL PROTECTED] (Ludovic Courtès) writes:
>
> I'd just suggest the following patch.
Beaut, I gave it a bit of a tweak and applied it.
(Incidentally, I'm sure this whole thread belongs on guile-devel, not
guile-user.)
___
Guile-user mailing list
Guil
Mike Gran <[EMAIL PROTECTED]> writes:
>
> numbers.lo: CFLAGS := $(filter-out -Werror,${CFLAGS})
That's not too flash is it.
> FWIW, this affects AIX as well, and is still present in
> Guile-1.6.8-rc0.
If Rob agrees I'd reckon it could be removed. -Werror isn't in a
default build anyway.
_
Greg Troxel <[EMAIL PROTECTED]> writes:
>
> I believe this should be fixed for 1.6.8; breaking slib breaks
> gnucash.
Ah. Do we have someone from the gnucash world who can say what it
should look like or how it should work?
___
Guile-user mailing list
Ok, we got there eventually. I checked it in, and I updated the docs
(have a read to see it they look right).
I want to give the docs a bit more polish, on the various constants
and the address endianness for a start, so don't worry if they're not
yet tip-top.
__
[EMAIL PROTECTED] (Ludovic Courtès) writes:
>
> Did you have a chance to look at that patch? :-)
He liked it before, I'll install it shortly, now your paperwork is on
file.
___
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/li
[EMAIL PROTECTED] (Ludovic Courtès) writes:
>
> Oh, right. Sorry about that. It turns out that I have both manuals
> (Info files) installed and I sometimes get to read the wrong one...
I removed it from the upcoming 1.6.8. Making all doc changes in both
branches is too much like hard work, but
1 - 100 of 136 matches
Mail list logo
