Re: Guile Logo License
Neil Jerram schrieb: 2008/7/12 Dave Page [EMAIL PROTECTED]: Hi there, I would like to create artwork for a free software project, using the cartoon gnu head from the Guile logo [1]. Please can you clarify the license used for this logo, so I know how to license my derivative work? If you have a higher-resolution version available, I would appreciate that. [1] http://www.gnu.org/software/guile/guile-title.jpg Martin, I believe you created this artwork; do you still own its copyright? If so, could you consider and respond to Dave's request? If not, do you recall under what terms you assigned it (presumably to FSF)? Hello Dave, hello bug-guile, I have now dual-licensed the artwork on this page: http://uebb.cs.tu-berlin.de/~magr/guile/guile-logo.en.html under the GPL/FDL. I plan to assign the copyright to the FSF, but that takes a little time as I'm on holidy now. Feel free to ask if anything is unclear. Martin signature.asc Description: OpenPGP digital signature
Re: define-syntax and vector constants
From: Bill Schottstaedt [EMAIL PROTECTED] Date: Tue, 19 Feb 2002 04:26:13 -0800 I think define-syntax is stumbling on vector constants: (use-modules (ice-9 syncase)) (define-syntax IF (syntax-rules () ((IF form1 form2) (if form1 form2)) ((IF form1 form2 form3) (if form1 form2 form3 (IF (not (vector? #(4.0))) (display oops)) invalid syntax #(4.0) In /usr/lib/snd/share/guile/1.7.0/ice-9/syncase.scm: 122: 0* [scm-error misc-error #f ~A ~S (invalid syntax #(4.0)) ()] (happens in Guile 1.4 also). This is not a bug in define-syntax, but on your code. R5RS requires vector constants to be quoted. Whether this makes sense or not is another question. (Note that Guile itself *does* accept unquoted vector constants, it's syncase which doesn't.) Try (IF (not (vector? '#(4.0))) (display oops)) For me this works. HTH, 'martin ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile
Install failure - missing libs
Hello list, don't know whether my setup at home is screwed or somthing changed with Guile's installation procedure. When I try to install te latest CVS version (both stable and unstable), some of the libraries don't get installed: libguile and libguilereadline. (Without the latter I could live, but not without the former :-) So the question is: anybody else with this problem? Or maybe a libtool versioning problem? Or stow is failing? I have made a make maintainer-clean; cvs update; ./autogen.sh; ./configure --enable-maintainer-mode --with-threads; make; su; make install prefix=/usr/local/stow/guile-1.5.4; cd /usr/local/stow; stow guile-1.5.4 Thanks, 'martin ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile
Re: CVS: module guile/guile-statprof can't be found
From: Fabrice Bauzac [EMAIL PROTECTED] Date: Sun, 06 Jan 2002 12:14:11 +0100 The page http://www.gnu.org/software/guile/anon-cvs.html says that there's a CVS module called guile/guile-statprof. When I tried to checkout, noon@noon:cvs:513$ cvs -z9 co guile/guile-statprof cvs server: cannot find module `guile/guile-statprof' - ignored cvs [checkout aborted]: cannot expand modules According to savannah, the module is named guile-statprof not guile/guile-statprof 'martin ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile
Re: bug
From: root [EMAIL PROTECTED] Date: Sat, 03 Nov 2001 12:09:12 -0500 I got a problem instaling guile all versions. It Error 1 somwhere in inet-aton I use Red Hat 7.1 Linux .Any hint will be helpful. Please see the relevant entry in the Guile FAQ at: http://www.gnu.org/software/guile/docs/faq/guile-faq.html#Building%20guile-1.4%20gives%20a%20previous%20declaration%20of%20inet_aton%20error%3f It also contains a workaround. Best regards, 'martin ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile
CVS guile does not build on Solaris+gcc
Hello folks,
these are the results on compiling a recent CVS Guile:
Making all in libguile
make[1]: Entering directory `/home/m/mgrabmue/cvs/guile/guile-core/libguile'
./guile-snarf -DHAVE_CONFIG_H -I.. -I./.. -I../libltdl -g -O2 -Wall
-Wmissing-prototypes numbers.c numbers.x \
|| { rm numbers.x; false; }
In file included from numbers.c:4334:
../libguile/num2integral.i.c:100: parse error
make[1]: *** [numbers.x] Error 255
make[1]: Leaving directory `/home/m/mgrabmue/cvs/guile/guile-core/libguile'
make: *** [all-recursive] Error 1
* This is the machine:
mgrabmue@fiesta (~/cvs/guile/guile-core): uname -a
SunOS fiesta 5.8 Generic_108528-09 sun4u sparc SUNW,Ultra-4
mgrabmue@fiesta (~/cvs/guile/guile-core): gcc --version
2.95.3
Guile 1.5.4 seems to build all right.
Best regards,
'martin
___
Bug-guile mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-guile
Re: Top-Level Debug/Backtrace Bug
From: Crowder, Brian [EMAIL PROTECTED] Date: Wed, 3 Oct 2001 16:48:56 -0700 It seems like erroneous code at the top-level of an .scm file fails to yield filenames and line-numbers for backtrace/error display. For example: echo error here test.scm guile --debug -l test.scm Yields something like Backtrace: In unknown file: ?: 0* [primitive-load test.scm] ?: 1* here unnamed port: In expression here: unnamed port: Unbound variable: here The reason is that the Guile reader only records source positions for cons cells. That means that a symbol like `here' will not have any source location attached, whereas a quotation like `'here' will. HTH, 'martin ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile
Re: guile.info: Writing
From: Thien-Thi Nguyen [EMAIL PROTECTED] Date: Thu, 4 Oct 2001 20:53:05 -0700 From: Alex Schroeder [EMAIL PROTECTED] Date: Mon, 24 Sep 2001 12:10:45 +0200 I just wanted some details on display but it was not in the R5RS Index. The node Writing has info on newline. I think display should be added to that node as well and an appropriate index entry should be available. we have different r5rs.info files, apparently. here, the index shows both display and newline in output. I'm not sure, but I think Alex was talking about the `R5RS Index' node in the GRM. 'martin ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile
Re: guile.info: Formatted Output
From: Alex Schroeder [EMAIL PROTECTED] Date: Sun, 23 Sep 2001 19:53:09 +0200 The node Formatted Output has a typo -- statr instead of start in the following paragraph: `~' Start a new line, that is, output a newline character if not already at the statr of a line. Fixed, thanks a lot! 'martin ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile
Re: guile.info: SRFI-13 - String Library
From: Alex Schroeder [EMAIL PROTECTED] Date: Mon, 24 Sep 2001 13:58:51 +0200 Typo in note SRFI-13 - String Library: * SRFI-13 Replicate/Rotate::Replacate and rotate portions of strings. should be * SRFI-13 Replicate/Rotate::Replicate and rotate portions of strings. Fixed. Thank you very much! Best regards, 'martin ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile
Re: guile.infoi: SRFI-13 - String Library
From: Alex Schroeder [EMAIL PROTECTED] Date: Mon, 24 Sep 2001 14:00:46 +0200 Suggestion: All of the procedures defined in SRFI-13, which are not already included in the Guile core library, are implemented in the module `(srfi srfi-13)'. The procedures which are both in Guile and in SRFI-13 are slightly extended. Their bindings overwrite those in the Guile core. I have committed this with a minor extension. Thank you again for your contributions. 'martin ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile
Re: Typo in ref. manual, @node lambda* Reference?
From: Eric Hanchrow [EMAIL PROTECTED] Date: 13 Aug 2001 13:23:49 -0700 I've only just started reading about keywords, and am not sure I've got this right. But it seems that every place in the documentation that says `#:key' should really say `#key' instead -- the former doesn't work in Guile; it complains like this: You are using Guile 1.4, the Reference Manual documents the behaviour of current CVS Guile. The NEWS file for upcoming Guile 1.6 says: ** Module (ice-9 optargs) now uses keywords instead of `#'. Instead of #optional, #key, etc you should now use #:optional, #:key, etc. Since #:optional is a keyword, you can write it as just :optional when (read-set! keywords 'prefix) is active. The old reader syntax `#' is still supported, but deprecated. It will be removed in the next release. Regards, 'martin ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile
CVS snapshot link
Hello folks, the link to the CVS snapshot on http://www.gnu.org/software/guile/ftp-snapshots.html does not work with by browser. It needs an additional slash at the end: ftp://krusty.e-technik.uni-dortmund.de/pub/guile/snapshots/ Dunno if my browser (Netscape 4.77) or the FTP server is the fault. Regards, 'martin ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile
module option :rename broken?
Hello folks, when cleaning up the examples directory, I found that my module examples do not work anymore. The problem can be reproduced with this example module: -=-=-=-=-=-=-=-=- (define-module (test)) (export foo bar) (define (foo) 1) (define (bar) 2) -=-=-=-=-=-=-=-=- When I use this module with the :rename option and `symbol-prefix-proc', the variable `foo' is exported without renaming, as shown below: guile mgrabmue@tortoise (~): guile guile (use-modules ((test) :rename (symbol-prefix-proc 'module-1:))) guile foo #procedure foo () guile module-1:foo unnamed port: In expression module-1:foo: unnamed port: Unbound variable: module-1:foo ABORT: (unbound-variable) Type (backtrace) to get more information or (debug) to enter the debugger. guile I hope someone can help me with that, I couldn't figure the problem out on my own. Regards, 'martin ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile
Problems with safe environments
Hello list, another problem discovered when checking the examples: guile (use-modules (ice-9 safe)) guile (define m (make-safe-module)) guile (eval '(define x 1) m) guile (quit) Some deprecated features have been used. Set the environment variable GUILE_WARN_DEPRECATED to detailed and rerun the program to get more information. Set it to no to suppress this message. Running with GUILE_WARN_DEPRECATED=detailed gives tons of [...] (You just re-exported `char-ci?' from `(ice-9 safe-r5rs)'.) (You just re-exported `char-ci=?' from `(ice-9 safe-r5rs)'.) (You just re-exported `char-ci=?' from `(ice-9 safe-r5rs)'.) (You just re-exported `char-alphabetic?' from `(ice-9 safe-r5rs)'.) [...] messages. (Compiling with --disable-deprecated does not work at all, because then `define' is not defined in safe environments.) Again, I don't know how to fix this. I tried replacing the `export' with `re-export' in null.scm, but this just gives an `unbound variable: unquote' error. Any thoughts? Regards, 'martin ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile
Re: couldnt compile guile
From: Joakim Verona [EMAIL PROTECTED] Date: Tue, 26 Jun 2001 10:21:39 +0200 while compilinng guile snapshot on 20010626, i got an error confilicting definitions of the function inet_aton in net_db.c. I just commented out the definition and it compiled ok. There was an existing definition in /usr/include/arpa/inet.h This is a known bug and fixed in CVS Guile. The workaround you described is correct for older versions of Guile. Thank you anyway for the report. Best regards, 'martin ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile
Re: Unable to make guile-1.3 (libguile)
From: Scott Ostrander [EMAIL PROTECTED] Date: Mon, 25 Jun 2001 09:51:00 -0500 Hello, perhaps you can point me in the correct direction or tell me what I'm doing wrong. I don't know about the errors you describe, but is there a reason you are trying to build such an old version of Guile? Could you try with a newer release, preferably 1.4? Thanks, 'martin ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile
Re: couldnt compile guile
Date: Tue, 26 Jun 2001 11:11:20 +0200 From: Joakim Verona [EMAIL PROTECTED] very odd, i downloaded the snapshot just an hour ago. i prefer snapshots due to our agressive firewall that makes tunneling cvs cumbersome. but thanks, i will download copies from cvs in the future. Oh dammit. I'm afraid I haven't read your report correctly. I didn't notice you were building a snapshot. It's just that I have seen this report so often for Guile 1.4 that I automatically respond to them. I should be more careful. But anyway, where did you download the snapshort from? www.glug.org or www.red-bean.com. The latter could be out of date, because it is (or was?) created from an outdated CVS repository, but I am not sure.. Maybe someone else can clear this up. Sorry for the confusion, 'martin ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile
`trace' is broken
Hello list, I was just trying out an example from the GRM, node `Trace': guile (define (rev ls) ... (if (null? ls) ... '() ... (append (rev (cdr ls)) (cons (car ls) '() guile (rev '(a b c d e)) (e d c b a) guile (trace rev) (rev) guile (rev '(a b c d e)) [rev (a b c d e)] ERROR: In procedure throw: ERROR: lazy-catch handler did return. ABORT: (misc-error) guile It would be really nice if we could get that working again before 1.6. Thanks, 'martin ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile
Re: compiling guile problem
From: [EMAIL PROTECTED]
Date: Thu, 24 May 2001 22:24:44 +0900
I'm having problem while compiling guile under RH Linux7.0 (gcc-2.95.3) from
guile-1.4.tar.gz distribution.
PATH=.:/usr/local/jdk1.3/bin:/usr/bin:/bin:/usr/X11R6/bin:/usr/local/bin:/op
t/bin:/usr/X11R6/bin:/home/vcholak/bin:/usr/local/TclPro1.4/linux-ix86/bin
./guile-doc-snarf net_db.c -DHAVE_CONFIG_H -I.. -I./.. -I../libltdl -g -O2
-Wall -Wmissing-prototypes net_db.c net_db.x \
|| { rm net_db.x; false; }
/bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I.. -I./..
-I../libltdl-g -O2 -Wall -Wmissing-prototypes -c net_db.c
rm -f .libs/net_db.lo
gcc -DHAVE_CONFIG_H -I.. -I./.. -I../libltdl -g -O2 -Wall
-Wmissing-prototypes -c net_db.c -fPIC -DPIC -o .libs/net_db.lo
net_db.c:85: conflicting types for `inet_aton'
/usr/include/arpa/inet.h:69: previous declaration of `inet_aton'
make[1]: *** [net_db.lo] Error 1
make[1]: Leaving directory `/usr/local/guile-1.4/libguile'
make: *** [all-recursive] Error 1
[root@bharat guile-1.4]#
This is a known problem on Red Hat 7.x and is fixed in current CVS.
As a workaround, simply comment out line 85 in net_db.c.
Regards,
'martin
___
Bug-guile mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-guile
Re: Compile Errors on Redhat 7.1
From: Clint Nelissen [EMAIL PROTECTED] Date: Mon, 21 May 2001 16:38:51 -0700 I get the following error when trying to compile Guile 1.4 on a Redhat 7.1 box: net_db.c:85: conflicting types for `inet_aton' /usr/include/arpa/inet.h:74: previous declaration of `inet_aton' make[1]: *** [net_db.lo] Error 1 make[1]: Leaving directory `/root/download/guile-1.4/libguile' make: *** [all-recursive] Error 1 I am not sure where the problem lies, but the same error occurs when trying to compile Guile 1.3.4. This is a known problem on Red Hat 7.1. The workaround is to simply comment out line 85 in net_db.c. In CVS Guile this is already fixed. Regards, 'martin ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile
Re: ifnottex?
From: Neil Jerram [EMAIL PROTECTED] Date: 16 May 2001 20:33:22 +0100 Masao == Masao Uebayashi [EMAIL PROTECTED] writes: Masao This is also from today's source compilation. Making all Masao in doc gmake[1]: Entering directory Masao `/usr/local/src/guile-core-20010517/doc' Updating Masao ./version.texi cd . \ makeinfo `echo guile.texi | sed Masao 's,.*/,,'` Making info file `guile.info' from `guile.texi'. Masao ./preface.texi:18: No matching `@end ifnottex'. [...] I've fixed the @itemize uses, but I'm confused by the @ifnottex errors, as preface.texi obviously does have the corresponding @end ifnottex lines. What version of makeinfo do you have? I also had that problem at university, where this makeinfo is installed: makeinfo (GNU texinfo 3.12) 1.68 Regards, 'martin ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile
Re: Cant unpack guile1.4 on Windows
From: Hrafnkell Eiriksson [EMAIL PROTECTED] Date: Tue, 8 May 2001 10:22:51 +0200 I cant unpack the guile-1.4.tar.gz archive on Windows with the GNU/Cygwin tools nor WinZip. I get the following error: [he@HRAFNKELL src]$ tar xfz guile-1.4.tar.gz tar: guile-1.4/ice-9/and-let*.scm: Cannot open: No such file or directory and an similar error from WinZip I guess this is because NTFS and FAT filesystems do not allow * as a part of the filename. Yes, that is exactly the reason. This is a known problem and fixed in CVS Guile. As a workaround, you would need to unpack the archive on a Unix-like system and then copy it to your Windows machine, renaming and-let*.scm to and-let-star.scm. After that, in the copied file, change the line (define-module (ice-9 and-let*)) to (define-module (ice-9 and-let-star)) and use (use-modules (ice-9 and-let-star)) if you want to use that module. Or, if you do not need that source file, simply ignore it. Guile itself does not depend on it (AFAIK). HTH, 'martin ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile
Re: skip_scsh_block_comment
From: Bill Schottstaedt [EMAIL PROTECTED] Date: Wed, 9 May 2001 07:27:00 -0700 Two minor things about the block comments: if you include a space after the closing !# you get an error (which strikes me as overly zealous), This could easily be changed, but it seems like this is by design, not by mistake. How do others think? (Maintainers?) and the error message calls these things scsh block comments -- is that intentional? Where do you see this error message? I can only find unterminated `#! ... !#' comment in the source. Regards, 'martin ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile
web page image tag broken
Hello list, could anyone w/ write privs please change the img tag in page_template.html to have an absolute path name? Otherwise, the image is not found for the subdirectory pages (mail/mail.html etc.) Thanks, 'martin ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile
CVS guile + module system broken
Hello list, mgrabmue@tortoise (~/cvs/guile/x/guile-1.4.1/libguile): GUILE_LOAD_PATH=~/cvs/guile/x/guile-1.4.1/ ./guile ERROR: In procedure set-current-module: ERROR: Wrong type argument in position 1: #f Is this because `set-current-module' and `current-module' are currently defined twice? (in boot-9.scm and modules.c) Regards, 'martin [ if this is just a transient error related to Marius' latest changes, ignore this post ] ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile
Re: Initial IPv6 support broken
From: Gary Houston [EMAIL PROTECTED] Date: 20 Apr 2001 07:28:23 - From: Martin Grabmueller [EMAIL PROTECTED] Date: Thu, 19 Apr 2001 22:24:34 +0200 Hello list, CVS Guile does not build here with the latest IPv6 changes: Thanks, I am not surprised. I'm following rfc2553 (March 1999) and it seems to work OK with recent linux/glibc. I guess a configure check for sin6_scope_id is in order: can you tell me what OS/version you are using so I can check for other differences? Debian GNU/Linux 2.2 mgrabmue@tortoise (~/cvs/guile): ls -l /lib/libc.so.6 lrwxrwxrwx1 root root 13 Sep 16 2000 /lib/libc.so.6 - libc-2.1.3.so 'martin ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile
Re: Vectors should not evaluate to themselves
From: Mikael Djurfeldt [EMAIL PROTECTED]
Date: 05 Apr 2001 01:12:28 +0200
Martin Grabmueller [EMAIL PROTECTED] writes:
according to R5RS, literally entered vectors do not evaluate to
themselves and must always be quoted. Guile does not detect this
error:
guile #(as)
#(as)
Should this be fixed, and can it be fixed easily?
It should be fixed and it is easy to fix. We only need to remove a
case in a switch at the top of the evaluator.
I have done that, but not committed yet. As I have never touched the
evaluator before, I am not sure if the attached patch is sufficient.
Also, R5RS only defines ``Numerical constants, string constants,
character constants and boolean constants'' (R5RS 4.1.2) as
self-evaluating, so the following cases should be removed, too:
case scm_tc7_smob:
case scm_tcs_closures:
case scm_tc7_cclo:
case scm_tc7_pws:
case scm_tcs_subrs:
and the `struct' part of the following:
case scm_tcs_cons_gloc: {
scm_bits_t vcell = SCM_STRUCT_VTABLE_DATA (x) [scm_vtable_index_vcell];
if (vcell == 0) {
/* This is a struct implanted in the code, not a gloc. */
RETURN (x);
} else {
proc = SCM_PACK (vcell);
SCM_ASRTGO (SCM_NIMP (proc), badfun);
#ifndef SCM_RECKLESS
#ifdef SCM_CAUTIOUS
goto checkargs;
#endif
#endif
}
break;
===File ~/cvs/guile/guile-core/libguile/diff-eval===
Index: eval.c
===
RCS file: /cvs/guile/guile-core/libguile/eval.c,v
retrieving revision 1.214
diff -r1.214 eval.c
2502,2516d2501
case scm_tc7_vector:
case scm_tc7_wvect:
#ifdef HAVE_ARRAYS
case scm_tc7_bvect:
case scm_tc7_byvect:
case scm_tc7_svect:
case scm_tc7_ivect:
case scm_tc7_uvect:
case scm_tc7_fvect:
case scm_tc7_dvect:
case scm_tc7_cvect:
#ifdef HAVE_LONG_LONGS
case scm_tc7_llvect:
#endif
#endif
___
Bug-guile mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-guile
Vectors should not evaluate to themselves
Hello list, according to R5RS, literally entered vectors do not evaluate to themselves and must always be quoted. Guile does not detect this error: guile #(as) #(as) Should this be fixed, and can it be fixed easily? Regards, 'martin ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile
Re: Documentation with GCC3.1, (was: build error on solaris)
From: Neil Jerram [EMAIL PROTECTED] Date: 23 Mar 2001 09:07:32 + "Neil" == Neil Jerram [EMAIL PROTECTED] writes: "Alexander" == Alexander Klimov [EMAIL PROTECTED] writes: Alexander The change which broke guile documentation is that Alexander [...] Neil I'm planning to try fixing this, mainly this Friday. Hmm... This is harder than I thought to fix elegantly. Two reasons suggest that it would be _wrong_ to try to use Guile to replace the Awk step here: (1) Guile startup time being quite slow. (2) Regexps are an optional feature when configuring Guile, so it seems unwise to assume that regexp and string matching procedures would be available. Any thoughts or ideas? (1) We could change the build stuff to fire up Guile once, and snarf all .x and .doc files in one run. That would probably break incremental building, though. (2) It's not only that we can't depend on regexp functions, we cannot depend that Guile is available at all, I think. A possibility would be to distribute the .x and .doc files, and only regenerate them if the corresponding .c files are changed. I f that's a good idea, I don't know. What about running some snarfing script (awk or guile) over the C sources instead of the output of the C preprocessor? The format of the C files (comments, SCM_DEFINEs etc.) is well suited for parsing. (not that I tried it already, though...) Regards, 'martin ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile
savannah.gnu.org cvs page
Hi all, don't know where the right place for this kind of report is, but maybe you guys want to know. 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 mgrabmue@tortoise (~/x): cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/guile co guile-core cvs server: cannot find module `guile-core' - ignored cvs [checkout aborted]: cannot expand modules Am I missing something? 'martin -- Martin Grabmueller [EMAIL PROTECTED] http://www.pintus.de/mgrabmue/ mgrabmue@#lkcc on EFnet ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile
Re: guile-core CVS and FTP snapshot version differ
From: Thomas Wawrzinek [EMAIL PROTECTED] Date: Fri, 9 Feb 2001 11:04:46 +0100 (MET) I just found that the nightly FTP snapshot of guile-core doesn't contain the oop subdirectory, whereas the CVS version has it. Is this intentional, or is the script building the snapshot just not aware that it shall include oop? I suppose that the snapshot scripts only do a `cvs update', so that new directories are not included (oop was created only a few months ago). Don't know who is creating those snapshots, but the scripts should be changed to do a cvs update -d Regards, 'martin -- Martin Grabmueller [EMAIL PROTECTED] http://www.pintus.de/mgrabmue/ mgrabmue@#lkcc on EFnet ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile
Properly handling smobs in macros.c
Hi all,
this is not really a bug, but I think the attached change should be
made for the sake of consistency.
2001-02-08 Martin Grabmueller [EMAIL PROTECTED]
* macros.c (scm_macro_name, scm_macro_transformer): Use
SCM_SMOB_DATA instead of SCM_CDR.
Regards,
'martin
===File ~/cvs/guile-core/libguile/diff-macro
Index: macros.c
===
RCS file: /cvs/guile/guile-core/libguile/macros.c,v
retrieving revision 1.24
diff -c -r1.24 macros.c
*** macros.c2000/12/08 17:32:56 1.24
--- macros.c2001/02/08 19:54:00
***
*** 148,169
SCM_DEFINE (scm_macro_name, "macro-name", 1, 0, 0,
(SCM m),
! "")
#define FUNC_NAME s_scm_macro_name
{
SCM_VALIDATE_SMOB (1,m,macro);
! return scm_procedure_name (SCM_CDR (m));
}
#undef FUNC_NAME
SCM_DEFINE (scm_macro_transformer, "macro-transformer", 1, 0, 0,
(SCM m),
! "")
#define FUNC_NAME s_scm_macro_transformer
{
SCM_VALIDATE_SMOB (1,m,macro);
! return SCM_CLOSUREP (SCM_CDR (m)) ? SCM_CDR (m) : SCM_BOOL_F;
}
#undef FUNC_NAME
--- 148,169
SCM_DEFINE (scm_macro_name, "macro-name", 1, 0, 0,
(SCM m),
! "Return the name of the macro @var{m}.")
#define FUNC_NAME s_scm_macro_name
{
SCM_VALIDATE_SMOB (1,m,macro);
! return scm_procedure_name (SCM_PACK (SCM_SMOB_DATA (m)));
}
#undef FUNC_NAME
SCM_DEFINE (scm_macro_transformer, "macro-transformer", 1, 0, 0,
(SCM m),
! "Return the transformer of the macro @var{m}.")
#define FUNC_NAME s_scm_macro_transformer
{
SCM_VALIDATE_SMOB (1,m,macro);
! return SCM_CLOSUREP (SCM_PACK(SCM_SMOB_DATA (m))) ? SCM_CDR (m) : SCM_BOOL_F;
}
#undef FUNC_NAME
___
Bug-guile mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-guile
Docstring patches.
Hello all,
I have added docstrings which were missing in the files struct.c,
weaks.c, srcprop.c and sort.c. The patch is attached below.
I thought about adding docstrings to all the remaining files which
lacked them, but before I do all the necessary work I would like to
hear from you if this is generally wanted, and if yes, if I do it The
Right Way, or if the docstrings can be improved.
Regards,
'martin
ChangeLog entry follows.
2001-01-29 Martin Grabmueller [EMAIL PROTECTED]
* struct.c (scm_make_vtable_vtable): Removed unnecessary "" from
end of docstring.
(scm_struct_set_x, scm_struct_vtable_tag, scm_struct_vtable_name,
scm_set_struct_vtable_name_x): Added docstrings.
* weaks.c (scm_make_weak_value_hash_table,
scm_make_doubly_weak_hash_table, scm_weak_value_hash_table_p,
scm_doubly_weak_hash_table_p):
* srcprop.c (scm_source_properties, scm_set_source_properties_x,
scm_source_property, scm_set_source_property_x): Added docstrings.
* sort.c (scm_sort_list_x, scm_restricted_vector_sort_x,
scm_sorted_p, scm_merge, scm_merge_x, scm_sort_x, scm_sort,
scm_stable_sort_x, scm_stable_sort, scm_sort_list_x,
scm_sort_list): Added docstrings.
===File ~/cvs/guile-core/libguile/doc-diff==
Index: sort.c
===
RCS file: /cvs/guile/guile-core/libguile/sort.c,v
retrieving revision 1.27
diff -u -r1.27 sort.c
--- sort.c 2000/11/17 16:25:04 1.27
+++ sort.c 2001/01/29 20:30:57
@@ -418,7 +418,10 @@
SCM_DEFINE (scm_restricted_vector_sort_x, "restricted-vector-sort!", 4, 0, 0,
(SCM vec, SCM less, SCM startpos, SCM endpos),
-"")
+ "Sort the vector @var{vec}, using @var{less} for comparing\n"
+ "the vector elements. @var{startpos} and @var{endpos} delimit\n"
+ "the range of the vector which gets sorted. The return value\n"
+ "is not specified.")
#define FUNC_NAME s_scm_restricted_vector_sort_x
{
size_t vlen, spos, len, size = sizeof (SCM);
@@ -447,7 +450,9 @@
* (not (less? (list-ref list i) (list-ref list (- i 1. */
SCM_DEFINE (scm_sorted_p, "sorted?", 2, 0, 0,
(SCM items, SCM less),
-"")
+ "Return @code{#t} iff @var{items} is a list or a vector such that\n"
+ "for all 1 = i = m, the predicate @var{less} returns true when\n"
+ "applied to all elements i - 1 and i")
#define FUNC_NAME s_scm_sorted_p
{
long len, j; /* list/vector length, temp j */
@@ -514,7 +519,12 @@
Note: this does _not_ accept vectors. */
SCM_DEFINE (scm_merge, "merge", 3, 0, 0,
(SCM alist, SCM blist, SCM less),
-"")
+ "Takes two lists @var{alist} and @var{blist} such that\n"
+ "@code{(sorted? alist less?)} and @code{(sorted? blist less?)} and\n"
+ "returns a new list in which the elements of @var{alist} and\n"
+ "@var{blist} have been stably interleaved so that\n"
+ "@code{(sorted? (merge alist blist less?) less?)}.\n"
+ "Note: this does _not_ accept vectors.")
#define FUNC_NAME s_scm_merge
{
long alen, blen; /* list lengths */
@@ -621,7 +631,13 @@
SCM_DEFINE (scm_merge_x, "merge!", 3, 0, 0,
(SCM alist, SCM blist, SCM less),
-"")
+ "Takes two lists @var{alist} and @var{blist} such that\n"
+ "@code{(sorted? alist less?)} and @code{(sorted? blist less?)} and\n"
+ "returns a new list in which the elements of @var{alist} and\n"
+ "@var{blist} have been stably interleaved so that\n"
+ " @code{(sorted? (merge alist blist less?) less?)}.\n"
+ "This is the destructive variant of @code{merge}\n"
+ "Note: this does _not_ accept vectors.")
#define FUNC_NAME s_scm_merge_x
{
long alen, blen; /* list lengths */
@@ -693,7 +709,11 @@
/* scm_sort_x manages lists and vectors, not stable sort */
SCM_DEFINE (scm_sort_x, "sort!", 2, 0, 0,
(SCM items, SCM less),
-"")
+ "Sort the sequence @var{items}, which may be a list or a\n"
+ "vector. @var{less} is used for comparing the sequence\n"
+ "elements. The sorting is destructive, that means that the\n"
+ "input sequence is modified to produce the sorted result.\n"
+ "This is not a stable sort.")
#define FUNC_NAME s_scm_sort_x
{
long len;/* list/vector length */
@@ -725,7 +745,9 @@
SCM_DEFINE (scm_sort, "sort", 2, 0, 0,
Re: 3 readline bugs: source positions, readline-options, endlessloop on error
Date: Thu, 25 Jan 2001 11:43:23 +0100 (MET)
From: Dirk Herrmann [EMAIL PROTECTED]
Two possible fixes came to my mind:
- Check the argument in `set-readline-input-port!' and only accept
valid open input ports.
- When the argument check in `%readline' fails, reset the current
input port to the standard input file port.
I think the first is preferable.
That's what I think, too. Could you provide a patch?
I modified the `set-readline-*put-port!' procedures (see below), but
got two questions:
- Is scm-error the right way to report the error? The output is
guile (set-readline-output-port! #t)
ERROR: In procedure set-readline-output-port!:
ERROR: Not an open output port: #t
ABORT: (wrong-type-arg)
, which seems okay to me.
- How can I test whether a given port is a file port? The problem is
that my patch works when you pass a stupid value like #t to the
procedures, but not for string ports, for example. They lead to the
same endless loop like before the patch.
(define-public (set-readline-input-port! p)
(if (and (input-port? p)
(not (port-closed? p)))
(set! input-port p)
(scm-error 'wrong-type-arg "set-readline-input-port!"
"Not an open input port: ~S"
(list p)
#f)))
(define-public (set-readline-output-port! p)
(if (and (output-port? p)
(not (port-closed? p)))
(set! output-port p)
(scm-error 'wrong-type-arg "set-readline-output-port!"
"Not an open output port: ~S"
(list p)
#f)))
Regards,
'Martin
--
Martin Grabmueller [EMAIL PROTECTED]
http://www.pintus.de/mgrabmue/ mgrabmue@#lkcc on EFnet
___
Bug-guile mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-guile
Doc patches
Hello, I have looked through the top-level doc files of guile-core, mainly to correct references to CVS repository locations, mailing lists etc., and corrected everything I found. I attached the output of `cvs diff -u'. Please tell me if you would like to get patches in another format. Thx, 'mgrabmue -- Martin Grabmueller [EMAIL PROTECTED] http://www.pintus.de/mgrabmue/ mgrabmue@#lkcc on EFnet ===File ~/cvs/guile-core/diff=== Index: ANON-CVS === RCS file: /cvs/guile/guile-core/ANON-CVS,v retrieving revision 1.11 diff -u -r1.11 ANON-CVS --- ANON-CVS1999/10/05 19:07:39 1.11 +++ ANON-CVS2000/12/20 14:29:26 @@ -24,12 +24,12 @@ 1) Install CVS version 1.9 or later on your system. 2) Log into the CVS server: - $ cvs -d :pserver:[EMAIL PROTECTED]:/cvs/guile login - At the prompt for `CVS password:', type `anoncvs'. + $ cvs -d :pserver:[EMAIL PROTECTED]:/cvs login + At the prompt for `CVS password:', simply press the enter key. Once you have logged in, your password is saved in ~/.cvspass, and you will not need to enter it again. 3) Check out a module: - $ cvs -z 9 -d :pserver:[EMAIL PROTECTED]:/cvs/guile checkout guile-core + $ cvs -z 9 -d :pserver:[EMAIL PROTECTED]:/cvs checkout guile-core This should create a new directory `guile-core' in your current directory, and populate it with the current Guile sources. 4) In the top directory of the source tree, run the command `./autogen.sh'. @@ -39,7 +39,6 @@ The modules available for checkout are: guile-core --- The scheme interpreter itself. guile-doc --- Guile documentation-in-progress. - guile-oops --- GOOPS Guile Object Oriented Programming System. guile-tcltk --- An interface between Guile and Tcl/Tk. guile-scsh --- An incomplete port of SCSH 0.4.4 to Guile. guile-rgx-ctax --- This has been discontinued; use Andrew Archibald's @@ -58,21 +57,13 @@ This will incorporate any changes the developers have made to Guile since your last update into your source tree. -The EGCS Project is kindly lending us space, time, and bandwidth on -their CVS server. Thanks, folks! - Change Notification == If you would like to receive mail when people commit changes to the -Guile CVS repository, you can subscribe to [EMAIL PROTECTED] -by sending a message to [EMAIL PROTECTED] Even -better, you can get daily digests of these commit messages by sending -a message to [EMAIL PROTECTED] - -If you want to subscribe an e-mail address other than the one that -appears in your From: header, say [EMAIL PROTECTED], send a mail note to [EMAIL PROTECTED] +Guile CVS repository, you can subscribe to [EMAIL PROTECTED] by using +the Mailman mailing list interface at +http://mail.gnu.org/mailman/listinfo/guile-cvs Questions @@ -107,5 +98,5 @@ tools we use to generate `configure', `aclocal.m4', and the `Makefile.in' files from their respective sources. Ideally, you shouldn't need to have them installed, if you don't want to change - those sources. If you do, see the section in `README' called + those sources. If you do, see the section in `HACKING' called `Hacking It Yourself'. Index: HACKING === RCS file: /cvs/guile/guile-core/HACKING,v retrieving revision 1.39 diff -u -r1.39 HACKING --- HACKING 2000/06/14 22:01:25 1.39 +++ HACKING 2000/12/20 14:29:28 @@ -36,7 +36,7 @@ - If you have put together a change that meets the coding standards described below, we encourage you to submit it to Guile. The best -place to post it is [EMAIL PROTECTED] Please don't send it +place to post it is [EMAIL PROTECTED] Please don't send it directly to me; I often don't have time to look things over. If you have tested your change, then you don't need to be shy. @@ -53,14 +53,14 @@ CVS conventions == - We use CVS to manage the Guile sources. The repository lives on -egcs.cygnus.com, in /cvs/guile; you will need an +subversions.gnu.org, in /cvs; you will need an account on that machine to access the repository. Also, for security -reasons, egcs presently only supports CVS connections via the SSH +reasons, subversions presently only supports CVS connections via the SSH protocol, so you must first install the SSH client. Then, you should set your CVS_RSH environment variable to ssh, and use the following as your CVS root: - :ext:[EMAIL PROTECTED]:/cvs/guile + :ext:[EMAIL PROTECTED]:/cvs Either set your CVSROOT environment variable to that, or give it as the value of the global -d option to CVS when you check out a working @@ -73,7 +73,6 @@ - guile-core --- the interpreter, QuickThreads, and ice-9 - guile-doc --- documentation
