Gambit-list Juillet 2005

gambit-list@iro.umontreal.ca

9 participants
12 discussions

Re: file-seek in Gambit.
by Marc Feeley 18 Sep '05

18 Sep '05

> I can't seem to find a way to seek in and get the position in files > using Gambit (4beta11). Wouldn't this be a handy feature? Yes, I have been planing this for a while and have just completed the implementation and documentation. Here it is: @deffn procedure input-port-byte-position @var{port} @r{[}@var{position} @r{[}@var{whence}@r{]}@r{]} @deffnx procedure output-port-byte-position @var{port} @r{[}@var{position} @r{[}@var{whence}@r{]}@r{]} When called with a single argument these procedures return the byte position where the next I/O operation would take place in the file attached to the given @var{port} (relative to the beginning of the file). When called with two or three arguments, the byte position for subsequent I/O operations on the given @var{port} is changed to @var{position}, which must be an exact integer. When @var{whence} is omitted or is 0, the @var{position} is relative to the beginning of the file. When @var{whence} is 1, the @var{position} is relative to the current byte position of the file. When @var{whence} is 2, the @var{position} is relative to the end of the file. The return value is the new byte position. On most operating systems the byte position for reading and writing of a given bidirectional port are the same. When @code{input-port-byte-position} is called to change the byte position of an input-port, all input buffers will be flushed so that the next byte read will be the one at the given position. When @code{output-port-byte-position} is called to change the byte position of an output-port, there is an implicit call to @code{force-output} before the position is changed. For example: @smallexample > @b{(define p @r{@i{; p is an input-output-port}} (open-file '(path: "test" char-encoding: latin1 create: maybe)))} > @b{(list (input-port-byte-position p) (output-port-byte-position p))} (0 0) > @b{(display "abcdefghij\n" p)} > @b{(list (input-port-byte-position p) (output-port-byte-position p))} (0 0) > @b{(force-output p)} > @b{(list (input-port-byte-position p) (output-port-byte-position p))} (11 11) > @b{(input-port-byte-position p 2)} 2 > @b{(list (input-port-byte-position p) (output-port-byte-position p))} (2 2) > @b{(peek-char p)} #\c > @b{(list (input-port-byte-position p) (output-port-byte-position p))} (11 11) > @b{(output-port-byte-position p -7 2)} 4 > @b{(list (input-port-byte-position p) (output-port-byte-position p))} (4 4) > @b{(write-char #\! p)} > @b{(list (input-port-byte-position p) (output-port-byte-position p))} (4 4) > @b{(force-output p)} > @b{(list (input-port-byte-position p) (output-port-byte-position p))} (5 5) > @b{(input-port-byte-position p 1)} 1 > @b{(read p)} bcd!fghij @end smallexample @end deffn > Also, while I'm making suggestions: Have you thought about > implementing a simple package system, for example something like > Chicken Scheme's eggs[3]? No. I'm not saying this wouldn't be useful, just that I haven't perceived a need for it yet. There's really nothing to change in Gambit itself to implement a package system like the one Chicken uses because Gambit's installation directory (/usr/local/Gambit-C) can be used for this. The subdirectory /usr/local/Gambit-C/package would store the installed packages, and the programs would use these packages like this: (include "~~/package/Xlib.scm") (include "~~/package/arrays.scm") ... or (load "~~/package/foo") The system extension file (~~/gambcext) could also be modified for the packages that need to permanently extend Gambit (this file is loaded whenever the interpreter is started). The most tedious in all of this is to implement the package management tool that installs the packages, compiles them if needed, checks for the latest version, checks package dependencies, etc. If you want to contribute such a tool please be my guest. What I can do is help you out in the design and host the packages that people contribute on Gambit's web site. Of course some of this work may have to be duplicated when the R6RS module system comes out... Marc

2 2

open-process in MinGW (beta14)
by Francois Magnan 23 Jul '05

23 Jul '05

Hi, Was anybody able to use the (open-process) command in Gambit4beta14 on the MinGW platform? Here is an example: ---------------- (define p (open-process (list path: "C:/msys/1.0/bin/ls.exe" arguments: (list "/") stderr-redirection: #t pseudo-terminal: #t ))) *** ERROR IN (stdin)(a)1.11 -- Can't convert result from C nonnull-pointer (open-process '(path: "C:/msys/1.0/bin/ls.exe" arguments: ("/") stderr-redirection: #t p...) --------------- It works well on MacOSX. I need a multiplatform way of calling a process with IO ports access. open-process should be the way but it seems to be broken in that version. Thank you, Francois Magnan

2 1

Compiling Gambit 40b14 on Cygwin
by Jens Axel Søgaard 18 Jul '05

18 Jul '05

I ran into problems compiling Gambit40b14 on Cygwin. The problem is similar the Lucier's on MacOS. ./configure --enable-single-host [omitted] js@js-dell ~/gambit/gambc40b14 $ make making all in include make[1]: Entering directory `/home/js/gambit/gambc40b14/include' make[1]: Leaving directory `/home/js/gambit/gambc40b14/include' making all in lib make[1]: Entering directory `/home/js/gambit/gambc40b14/lib' gcc -I../include -I. -Wall -W -Wno-unused -O1 -fno-math-errno -fschedule-insns2 -fno-trapping-math -fno-strict-aliasing -fwrapv -fomit-frame-pointer -fPIC -fno-common -mieee-fp -DHAVE_CONFIG_H -D___PRIMAL -D___LIBRARY -D___GAMBCDIR=\"/usr/l ocal/Gambit-C\" -c main.c main.c:1: warning: -fPIC ignored for target (all code is position independent) gcc -I../include -I. -Wall -W -Wno-unused -O1 -fno-math-errno -fschedule-insns2 -fno-trapping-math -fno-strict-aliasing -fwrapv -fomit-frame-pointer -fPIC -fno-common -mieee-fp -DHAVE_CONFIG_H -D___PRIMAL -D___LIBRARY -D___GAMBCDIR=\"/usr/l ocal/Gambit-C\" -c setup.c setup.c:1: warning: -fPIC ignored for target (all code is position independent) gcc -I../include -I. -Wall -W -Wno-unused -O1 -fno-math-errno -fschedule-insns2 -fno-trapping-math -fno-strict-aliasing -fwrapv -fomit-frame-pointer -fPIC -fno-common -mieee-fp -DHAVE_CONFIG_H -D___PRIMAL -D___LIBRARY -D___GAMBCDIR=\"/usr/l ocal/Gambit-C\" -c mem.c mem.c:1: warning: -fPIC ignored for target (all code is position independent) gcc -I../include -I. -Wall -W -Wno-unused -O1 -fno-math-errno -fschedule-insns2 -fno-trapping-math -fno-strict-aliasing -fwrapv -fomit-frame-pointer -fPIC -fno-common -mieee-fp -DHAVE_CONFIG_H -D___PRIMAL -D___LIBRARY -D___GAMBCDIR=\"/usr/l ocal/Gambit-C\" -c c_intf.c c_intf.c:1: warning: -fPIC ignored for target (all code is position independent) gcc -I../include -I. -Wall -W -Wno-unused -O1 -fno-math-errno -fschedule-insns2 -fno-trapping-math -fno-strict-aliasing -fwrapv -fomit-frame-pointer -fPIC -fno-common -mieee-fp -DHAVE_CONFIG_H -D___PRIMAL -D___LIBRARY -D___GAMBCDIR=\"/usr/l ocal/Gambit-C\" -c os.c os.c:1: warning: -fPIC ignored for target (all code is position independent) os.c: In function `___os_host_info': os.c:317: warning: passing arg 1 of `___CHARSTRING_to_SCMOBJ' discards qualifiers from pointer target type gcc -I../include -I. -Wall -W -Wno-unused -O1 -fno-math-errno -fschedule-insns2 -fno-trapping-math -fno-strict-aliasing -fwrapv -fomit-frame-pointer -fPIC -fno-common -mieee-fp -DHAVE_CONFIG_H -D___PRIMAL -D___LIBRARY -D___GAMBCDIR=\"/usr/l ocal/Gambit-C\" -c os_base.c os_base.c:1: warning: -fPIC ignored for target (all code is position independent) gcc -I../include -I. -Wall -W -Wno-unused -O1 -fno-math-errno -fschedule-insns2 -fno-trapping-math -fno-strict-aliasing -fwrapv -fomit-frame-pointer -fPIC -fno-common -mieee-fp -DHAVE_CONFIG_H -D___PRIMAL -D___LIBRARY -D___GAMBCDIR=\"/usr/l ocal/Gambit-C\" -c os_time.c os_time.c:1: warning: -fPIC ignored for target (all code is position independent) gcc -I../include -I. -Wall -W -Wno-unused -O1 -fno-math-errno -fschedule-insns2 -fno-trapping-math -fno-strict-aliasing -fwrapv -fomit-frame-pointer -fPIC -fno-common -mieee-fp -DHAVE_CONFIG_H -D___PRIMAL -D___LIBRARY -D___GAMBCDIR=\"/usr/l ocal/Gambit-C\" -c os_shell.c os_shell.c:1: warning: -fPIC ignored for target (all code is position independent) gcc -I../include -I. -Wall -W -Wno-unused -O1 -fno-math-errno -fschedule-insns2 -fno-trapping-math -fno-strict-aliasing -fwrapv -fomit-frame-pointer -fPIC -fno-common -mieee-fp -DHAVE_CONFIG_H -D___PRIMAL -D___LIBRARY -D___GAMBCDIR=\"/usr/l ocal/Gambit-C\" -c os_files.c os_files.c:1: warning: -fPIC ignored for target (all code is position independent) gcc -I../include -I. -Wall -W -Wno-unused -O1 -fno-math-errno -fschedule-insns2 -fno-trapping-math -fno-strict-aliasing -fwrapv -fomit-frame-pointer -fPIC -fno-common -mieee-fp -DHAVE_CONFIG_H -D___PRIMAL -D___LIBRARY -D___GAMBCDIR=\"/usr/l ocal/Gambit-C\" -c os_dyn.c os_dyn.c:1: warning: -fPIC ignored for target (all code is position independent) gcc -I../include -I. -Wall -W -Wno-unused -O1 -fno-math-errno -fschedule-insns2 -fno-trapping-math -fno-strict-aliasing -fwrapv -fomit-frame-pointer -fPIC -fno-common -mieee-fp -DHAVE_CONFIG_H -D___PRIMAL -D___LIBRARY -D___GAMBCDIR=\"/usr/l ocal/Gambit-C\" -c os_tty.c os_tty.c:1: warning: -fPIC ignored for target (all code is position independent) gcc -I../include -I. -Wall -W -Wno-unused -O1 -fno-math-errno -fschedule-insns2 -fno-trapping-math -fno-strict-aliasing -fwrapv -fomit-frame-pointer -fPIC -fno-common -mieee-fp -DHAVE_CONFIG_H -D___PRIMAL -D___LIBRARY -D___GAMBCDIR=\"/usr/l ocal/Gambit-C\" -c os_io.c os_io.c:1: warning: -fPIC ignored for target (all code is position independent) os_io.c:2944:1: warning: "TCP_NODELAY" redefined In file included from /usr/include/sys/socket.h:15, from os.h:137, from os_base.h:8, from os_io.c:14: /usr/include/cygwin/socket.h:166:1: warning: this is the location of the previous definition os_io.c: In function `open_full_duplex_pipe2': os_io.c:4765: error: `TIOCSCTTY' undeclared (first use in this function) os_io.c:4765: error: (Each undeclared identifier is reported only once os_io.c:4765: error: for each function it appears in.) make[1]: *** [os_io.o] Error 1 make[1]: Leaving directory `/home/js/gambit/gambc40b14/lib' make: *** [all-recursive] Error 1 -- Jens Axel Søgaard

1 0

Re: cadar: compiler bug?
by Marc Feeley 16 Jul '05

16 Jul '05

On 15-Jul-05, at 8:18 PM, Sven.Hartrumpf(a)fernuni-hagen.de wrote: > Hi all. > > I managed to isolate a long standing problem for my programs: > > >> cat a.scm >> > (write (cadar (read))) > >> gsc a.c >> gcc344 a.c a_.c -lgambc -lm -lutil -ldl >> echo "((11 12 13) (21 22 23) (31 32 33))" | a.out >> > 21 > > The result of the interpreter looks much better: > 12 > > Current beta of Gambit (and before), Linux i386, gcc 3.4.4. > > Hope this helps. > > Greetings > Sven > Oh my... what a stupid mistake! To fix it you will have to make the following change to gsc/_t- c-2.scm and recompile the compiler (with a "make"). Change the definition (define (gen-c...r pattern var) (if (< pattern 4) (gen-tst-pair pattern var (new-cst source env #f) check-run-time-binding) (let ((vars (gen-temp-vars source '(#f)))) (new-call source env (gen-prc source env vars (gen-c...r (quotient pattern 2) (car vars))) (list (gen-tst-pair pattern var (new-cst source env #f) #f)))))) to (define (gen-c...r pattern var) (if (< pattern 4) (gen-tst-pair pattern var (new-cst source env #f) check-run-time-binding) (let ((vars (gen-temp-vars source '(#f)))) (new-call source env (gen-prc source env vars (gen-tst-pair pattern (car vars) (new-cst source env #f) #f)) (list (gen-c...r (quotient pattern 2) var)))))) Marc

2 1

Need to reverse order of constant propagation and specialization
by Bradley Lucier 15 Jul '05

15 Jul '05

Marc: Consider the following code: (declare (standard-bindings)(extended-bindings)(block)) (define (expt1 a b) (define (square x) (* x x)) (cond ((= b 0) 1) ((even? b) (square (expt1 a (quotient b 2)))) (else (* a (square (expt1 a (quotient b 2))))))) (declare (inlining-limit 100000)) (define a (expt1 2 20)) (define b (expt1 2 40)) (define c (expt1 2 80)) When compiled, this gives peano-71% gsc -c -expansion crap loading /pkgs/Gambit-C/gambcext.scm Expansion: (define expt1 (lambda (a b) (if (if (and (##fixnum? b) #t) (##fixnum.= b 0) (= b 0)) 1 (if (even? b) (let ((x (expt1 a (or (and (##fixnum? b) (##fixnum.quotient? b 2)) (quotient b 2))))) (or (and (##fixnum? x) (and (##fixnum? x) (##fixnum.*? x x))) (* x x))) (let ((temp (let ((x (expt1 a (or (and (##fixnum? b) (##fixnum.quotient? b 2)) (quotient b 2))))) (or (and (##fixnum? x) (and (##fixnum? x) (##fixnum.*? x x))) (* x x))))) (or (and (##fixnum? a) (and (##fixnum? temp) (##fixnum.*? a temp))) (* a temp))))))) (define a 1048576) (define b (or (##fixnum.*? 1048576 1048576) 1099511627776)) (define c (let ((x (or (##fixnum.*? 1048576 1048576) 1099511627776))) (or (and (##fixnum? x) (and (##fixnum? x) (##fixnum.*? x x))) (* x x)))) Note how a is completely determined, b has the code it has because (##fixnum.*? 1048576 1048576) could be #t or #f depending on whether Gambit was compiled for 32-bit or 64-bit machines, etc. It seems that the expansion of *, +, etc., was done before the constant propagation and evaluation of known functions. This should be reversed, and a, b, and c should all be reduced to constants in the compile. Brad

1 1

Gambit-C 4.0 beta 14
by Marc Feeley 15 Jul '05

15 Jul '05

A new beta of Gambit-C 4.0 is now available in source form at this address: http://www.iro.umontreal.ca/~feeley/gambc40b14.tar.gz Here's what's new: - Binary serialization. The procedures object->u8vector and u8vector->object implement binary serialization and deserialization. The representation used is 2 to 3 times more compact than text serialization. Moreover, these procedures are implemented more efficiently, with tables, which makes binary serialization and deserialization two orders of magnitude faster than text serialization. - Better conformance to the draft "R6RS Unicode data" SRFI. The range of the character type has been extended to #x10FFFF. Each character in a string now occupies 4 bytes of memory. The size of characters can be changed by redefining the macro ___MAX_CHR in gambit.h and recompiling the system. ___MAX_CHR can be 0xFF (1 byte per character), 0xFFFF (2 bytes per character), or 0x10FFFF (4 bytes per character). The syntax for characters, quoted strings and "here strings" proposed in the SRFI have been implemented, and the old #\#x1234 syntax for characters has been removed (you should now use #\u1234 instead). - Improvements to the Gambit compiler. A minor modification to the code generator has improved the register allocation. The inlining of arithmetic procedures (+, -, *, ...) has been improved. For example, the program (define (triple x) (* x 3)) (define (make-multiplier x) (lambda (y) (* x y))) is expanded to (define triple (lambda (x) (if (and (##eq? * '#<procedure #2 *>) (##fixnum? x)) (let ((temp (##fixnum.*? x 3))) (if temp temp (* x 3))) (* x 3)))) (define make-multiplier (lambda (x) (lambda (y) (if (and (##eq? * '#<procedure #2 *>) (and (##fixnum? y) (##fixnum? x))) (if (##fixnum.= y 0) 0 (let ((temp (if (##fixnum.= y -1) (##fixnum.-? x) (##fixnum.*? x y)))) (if temp temp (* x y)))) (* x y))))) - Testing tables for equality. Tables can be compared for equality using the equal? procedure. Two tables X and Y are considered equal by equal? when they have the same weakness attributes, the same key comparison procedure, the same hashing procedure, the same length, and for all the keys k in X, (equal? (table-ref X k) (table-ref Y k)). - Compiled scripts now behave the same as interpreted scripts. The "main" procedure will be called automatically, the language will be set according to the first line of the script, and the value returned by the procedure "command-line" will be the list of command line arguments after the script filename. Scripts can also be compiled to an executable program. - Process port fixes. Several problems with process ports have been fixed, in particular when pseudo-terminal: is #t. This makes it easy for a Scheme program to interact with programs that were designed to be used interactively. Here is an example: > (define p (open-process (list path: "/sw/bin/emacs" arguments: '("-nw") pseudo-terminal: #t))) > (read-line p) "\33[?1049h\33[?12;25h\33[?1h\33=\33[23;1H\33[?25l\33[7m----:--- F1 ..." - Documentation checking. A script now checks that the documentation is consistent with the behavior of the system. This has helped uncover many inconsistencies. Unfortunately only a few of the inconsistencies have been fixed at this point. Marc

2 1

RE: [gambit-list] Process Accounting
by Logan, Patrick D 15 Jul '05

15 Jul '05

This would be an interesting feature to see in Termite. Is that system going to be made available? -Patrick http://lisp-ecoop05.bknr.net/pdf/19654 (PDF) http://www.iro.umontreal.ca/~boucherd/mslug/meetings/20050216/termite.pd f -----Original Message----- Is there any way to do any sort of process accounting in gambit? I am playing around with the idea of migrating work based on resource consumption of a particular job and overall load. To do this I need some form of self monitering. Insights and suggestions are welcome.

1 0

Process Accounting
by Eric Merritt 15 Jul '05

15 Jul '05

Guys, Is there any way to do any sort of process accounting in gambit? I am playing around with the idea of migrating work based on resource consumption of a particular job and overall load. To do this I need some form of self monitering. Insights and suggestions are welcome.

1 0

RE: [gambit-list] Gambit 4.0 under MS Windows
by Dan Hristodorescu 14 Jul '05

14 Jul '05

Hi Mark, You can use the project files in the Gambit directory/misc/proj_msc.zip You just have to add "./include" to include directories, delete all files from the project and add all files in lib and gsi (gsc) based on the project you use (for gsi or gsc). You also have to add the winsock library (ws2_32) to the libs. It works fine in b12 but when I tried with b13 I got errors: c:\gambc40b13\lib\_io.c(10369) : error C2065: '___REGISTER_HOST_ENTRY' : undeclared identifier c:\gambc40b13\lib\_io.c(10369) : error C2146: syntax error : missing ';' before identifier '___jump' Scott Graham posted the the VC 7.1 projects for b13 on 5/14/2005 in the forum, you can search for his message. He fixed the compilation for b13 and I hope it works fine. If b13 doesn't work for you, you can use b12 but be aware there is a fix for console redirection you have to apply if you use it in an application compiled for the graphical subsystem (non console mode). Marc posted it in the forum a while ago. Also in b12 if you compile it in C++ mode you'll have to fix some compilation errors, mostly casts and a couple of nested functions you have to move outside. I hope it helps, Dan. -----Original Message----- From: mark_shirley(a)comcast.net [mailto:mark_shirley@comcast.net] Sent: Wednesday, July 13, 2005 10:09 PM To: dhristodorescu(a)borderfree.com Cc: gambit-list(a)iro.umontreal.ca Subject: RE: [gambit-list] Gambit 4.0 under MS Windows Wrom: LBXFGGMEPYOQKEDOTWFAOB I used mingw on Windows, the latest beta 13 can be compiled without problems even when using C++ (--enable-cplusplus). I haven't compiled b13 with Visual Studio but I compiled b12 and I had to fix the file reference in the project but tha's fairly easy. Regards, Dan Hristodorescu. Dan, Thank you. That gives me some hope. I want to compile Gambit with Visual Studio, because my end goal is to build it as a library which can be linked into a larger system system that builds under VS. Doing them all in the same framework will make my life easier. You compiled b12 under VS. Since there's no makefile or project for VS yet, can you say more about what you had to do to do that? Which project file did you fix a reference in? Can you send me your prj and sln files for b12? (I believe I haven't gotten the compiler directives correct, and particularly the defines used by the various macros.) I got b11 compiled under Visual Studio, but it was easy. I just started an empty project, added the compiler and interpreter .c files, and it almost compiled. Some tweaks and I was done. This time, I'm getting syntax errors because macros aren't defined. Since the tree of DEFINEs is complex, I'm trying to find out where to get a set of commandline args for a compile by visual studio. Any suggestions would be very welcome. Thanks, Mark

1 0

RE: [gambit-list] Gambit 4.0 under MS Windows
by Dan Hristodorescu 13 Jul '05

13 Jul '05

I used mingw on Windows, the latest beta 13 can be compiled without problems even when using C++ (--enable-cplusplus). I haven't compiled b13 with Visual Studio but I compiled b12 and I had to fix the file reference in the project but tha's fairly easy. Regards, Dan Hristodorescu. -----Original Message----- From: gambit-list-bounces(a)iro.umontreal.ca [mailto:gambit-list-bounces@iro.umontreal.ca] On Behalf Of Mark H. Shirley Sent: Tuesday, July 12, 2005 11:03 AM To: gambit-list(a)iro.umontreal.ca Subject: [gambit-list] Gambit 4.0 under MS Windows Hello, Is anyone compiling the recent Gambit 4.0 betas under MS windows? I'm interested in trying to use it (integrating it with some other software) and I don't want to reinvent the wheel wrt the make files or visual studio project files. Thank you, Mark Shirley _______________________________________________ Gambit-list mailing list Gambit-list(a)iro.umontreal.ca http://mailman.iro.umontreal.ca/mailman/listinfo/gambit-list

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Gambit-list Juillet 2005