Gambit-list Décembre 2007

gambit-list@iro.umontreal.ca

20 participants
25 discussions

Cygwin for Gambit mini-howto
by Bob McIsaac 10 Déc '07

10 Déc '07

Cygwin for Gambit mini-howto: 1. default install of cygwin 2. repeat install.. select the following packages:- a. gcc core b. make c. diffutils 3. open cygin shell from desktop icon 4. configure Gambit source with gcc options 5. make, make check, make install ( my check on winxp said all tests passed) Cheers, -Bob-

1 0

Re: [gambit-list] [MSLUG] Significance of 'C' in "Gambit-C"
by Marc Feeley 09 Déc '07

09 Déc '07

On 8-Dec-07, at 1:05 PM, Bradley Lucier wrote: > I believe the answer is roughly as follows. > > There were various versions of Gambit that generated 68020 code for > early macintoshes and BBN Butterfly computers, for example; the > version that is now "Gambit" started as the version that generated > "C" code, hence "Gambit-C". > > Brad That's the closest to the real answer. Gambit (without the C suffix) is the generic name of the system which spans all possible target platforms. Up to now only two target platforms have been supported: initially Gambit had a back-end generating Motorola 68020 code (Sun workstation, Apple Macintosh, BBN butterfly multiprocessor, etc), then around 1994 a back-end generating C code was introduced. When the C back-end was released I decided to distinguish the systems with a suffix, so Gambit-68K was the first system and Gambit-C is the one generating C code. Note that at that point both front ends were identical, but the front-end of Gambit-C has evolved to support the C FFI and other extensions. I haven't worked on Gambit-68K in a long time, because my focus has shifted to portability rather than raw performance. Portability is the primary concern, followed by featurefullness, followed by performance. I think that's what most users want. Gambit-C is very portable, it works on any system with a decent C compiler (all the major workstations are covered of course, but Gambit-C has also been used on unusual target platforms such as the embedded PowerPC processor in Xilinx FPGAs and the ARM processor on the Nintendo DS). Gambit-C's abstraction of the target platform allows using it as a virtual machine (so that the same program will work on Unix, MacOS, Windows, and other systems with no modifications). Sorry, I'm rambling... Marc

2 2

The challenge of Scheme for Windows
by Bob McIsaac 06 Déc '07

06 Déc '07

Hi: I enjoy using Gambit on Linux but have no luck doing same on windows. I tried v401 with openwatcom. It failed because the platform-dependent header files need to be somehow configured. On v410 prebuilt, gsi works but there is an apparent linkage error with gsc. Perhaps there is some issue with my win32 environment. This is not to dis Gambit, Chicken Scheme presents the same sort of Windows headaches. It might be less challenging if Scheme for windows relied only on a single free win32 compiler such as Openwatcom. Then there would not be the extra complexity of setting up Mingw or Cygwin. -Bob- C:\SCHEME\RFB>gcc -v Reading specs from C:/bins/MinGW/bin/../lib/gcc/mingw32/3.4.2/specs Configured with: ../gcc/configure --with-gcc --with-gnu-ld --with-gnu-as --host= mingw32 --target=mingw32 --prefix=/mingw --enable-threads --disable-nls --enable -languages=c,c++,f77,ada,objc,java --disable-win32-registry --disable-shared --e nable-sjlj-exceptions --enable-libgcj --disable-java-awt --without-x --enable-ja va-gc=boehm --disable-libgcj-debug --enable-interpreter --enable-hash-synchroniz ation --enable-libstdcxx-debug Thread model: win32 gcc version 3.4.2 (mingw-special) C:\SCHEME\RFB>tmake c:/shared/gambit/v410/bin/gsc.exe -c tfile.scm c:/shared/gambit/v410/bin/gsc.exe -link tfile.c *** ERROR IN ##parameterize -- No such file or directory (current-directory "c:\\lib") TMAKE: *** [all] Error 0x46 C:\SCHEME\RFB>path PATH=C:\shared\gambit\v410\bin;C:\bins\MinGW\bin;C:\WINDOWS\System32;c:\ util;c:\bins\ATT\Graphviz\bin;c:\bins\doxygen\bin

2 1

Remote REPL
by James Long 06 Déc '07

06 Déc '07

I am writing some code that enables Gambit's REPL to be used remotely on any Termite node using remote (or process) ports. I'm am sure others have done this, but I haven't been able to find any working code. It's working very well. Right now, you just fire up a normal gsi session, find your node, and say `(make-repl the-node)` and you have a REPL which is being evaluated on that node. I have attached the code to the bottom of this email. It is the result of studying the web-repl example and another post on this list about non-repl debugging (https://webmail.iro.umontreal.ca/pipermail/gambit-list/2007-August/001670.h…), and eating some chocolate chip cookies too. The main problem, however, is that debugging isn't working. When any kind of error happens, it just hangs and the repl worker doesn't give me anything. Usually it opens up a new sub-repl, but I'm not exactly sure how this is different than the initial repl call - and _repl.scm is quite a beast! The strange thing is that it works in the web-repl and probably the other one I previously mentioned. The biggest difference may be that the repl worker here isn't running on the primordial thread. Thanks! (The 'proc-port' stuff is the same as any ports, except it operates on the termite remote ports. Eventually I'll override the standard input/output/error ports and use these for everything. It looks like Termite did that at one point but for some reason all of that is commented out...) ;;;;; --- REMOTE REPL --- (define (start-repl-worker-input-output repl-input-proc-port repl-output-proc-port repl-worker-port) (spawn (lambda () (let loop1 () (let loop2 ((line '())) (let ((c (proc-port-read-char repl-input-proc-port))) (if (char? c) (cond ((or (char=? c #\newline) (char=? c #\return)) (display (list->string (reverse line)) repl-worker-port) (write-char #\return repl-worker-port) (write-char #\linefeed repl-worker-port) (force-output repl-worker-port) (loop1)) (else (loop2 (cons c line)))))))))) (spawn (lambda () (let loop1 () (let ((c (read-char repl-worker-port))) (proc-port-write-char c repl-output-proc-port) (loop1)))))) (define (make-repl node) (let ((op (current-output-proc-port)) (ip (current-input-proc-port)) (repl (self))) (remote-spawn node (lambda () (receive (pipe1 pipe2) (open-string-pipe) (display "Starting repl io...\n") (start-repl-worker-input-output ip op pipe1) (display "Setting repl channel...\n") (set! ##thread-make-repl-channel (lambda () (##make-repl-channel-ports pipe2 pipe2))) (display "Firing up repl...\n") (##repl-debug-main))))) (?? (lambda (o) (eq? o 'quit)))) -- James Long Coptix, Inc. longster(a)gmail.com

3 12

{Spam?} what is ## for?
by Li Xiangyang 03 Déc '07

03 Déc '07

I see a lot of ## included in library file, such as ##define-macro, ##include, what does that mean? I can't find any explanation in documents. thanks! Howard _________________________________________________________________ Discover the new Windows Vista http://search.msn.com/results.aspx?q=windows+vista&mkt=en-US&form=QBRE

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Gambit-list Décembre 2007