- Gambit-list - mailman.iro.umontreal.ca

blackhole question
by Milos Negovanovic 01 Aoû '10

01 Aoû '10

Hi all, I am new to scheme, gambit and blackhole! Have a look at the fallowing example: milosn@box gambit $ cat a.scm (define (test) (println "A!")) milosn@box gambit $ cat b.scm (define (test) (println "B!")) milosn@box gambit $ cat mod.scm (import a b) (test) milosn@box gambit $ bsc -i mod.scm Loaded Black Hole. A! My question is: why is it printing "A!" when test procedure was redefined in b.scm and b.scm is imported after a.scm? Regards -- Milos Negovanovic milos.negovanovic(a)gmail.com

2 1

Macros and standard
by Yves Parès 01 Aoû '10

01 Aoû '10

Hello! I'm new to scheme and gambit. I've read "A tour of scheme in Gambit", and now I'm learning the language through "The scheme programming language" ( http://www.scheme.com/tspl3/) My question concerns define-syntax VS define-macro. If I understood well, the first is standard scheme (*) whereas the latter is not. Besides, "A tour of scheme in Gambit" qualifies define-macro as "unhygienic" (**). Moreover (as I am from Haskell), I find define-syntax's pattern-matching simpler. So: 1) What is the point of define-macro? Why does "A tour of Scheme in Gambit" encourages to use it, since it doesn't detail define-syntax? 2) Why does gambit run by default in a non-standard mode (Gambit scheme, gsc -:S) in which define-syntax doesn't exist whereas it is standard? 3) I plan to use termite, which uses Gambit Scheme and not standard scheme (gsc -:s). Can gambit scheme code call to procedures written in standard scheme? Thanks! (*) By 'standard' I mean R5RS. (**) Word which, from my newbie point of view, kind of sounds like "evil" or "don't-you-touch-it".

3 3

Termite and Gambit 4.6.0
by Jeronimo Pellegrini 23 Jul '10

23 Jul '10

Hello, The paper [1] that describes Termite mentions a macro "catch" that doesn't seem to be defined anywhere in Termite sources: > (node-init (make-node "127.0.0.1" 40000)) ok > (catch (lambda (exception) #t) (spawn (lambda () (raise 'error))) (? 1 'ok) #f) *** ERROR IN (console)(a)2.2 -- Unbound variable: catch 1> (This is an example from the Termite paper) I was wondering if this macro existed in some previous version of Gambit, or if it's just not implemented in Termite. If it is from some old version of Gambit, what would it be? (I've already reported a bug on Termite) Thanks, J. [1] http://termite.googlecode.com/files/termite.pdf

1 0

windows problem
by 赵常坤 22 Jul '10

22 Jul '10

hi, I'm a beginner of gambit. I build an "hello world" under win7, but it always open a new console to show the result, how can I make it display at the current console, just like a "normal" console exe. [?]

2 1

[ANN] Call for Participation for 2010 Workshop on Scheme and Functional Programming
by sfp2010＠iro.umontreal.ca 17 Jul '10

17 Jul '10

[my apologies if you receive multiple copies of this email.] CALL FOR PARTICIPATION 2010 Workshop on Scheme and Functional Programming Montreal, Quebec, Canada Saturday and Sunday August 21-22, 2010 http://www.iro.umontreal.ca/~sfp2010 *** ONLINE REGISTRATION IS NOW OPEN FOR THE WORKSHOP *** *** REGISTER BEFORE AUGUST 10 TO AVOID LATE REGISTRATION FEES *** PURPOSE The 2010 Workshop on Scheme and Functional Programming provides a forum for discussing experience with and future development of the Scheme programming language. The scope of the workshop includes all aspects of the design, implementation, theory, and application of Scheme. We encourage everyone interested in Scheme to participate. FORMAT The workshop will be held on the Université de Montréal campus Saturday and Sunday August 21-22, 2010. The workshop will start at 8 AM August 21 and end around noon on August 22. This year's departure from the traditional one day format will leave room for special events (lightning talks, social outing, etc). *** IF YOU ARE INTERESTED IN GIVING A LIGHTNING TALK, PLEASE CONTACT THE WORKSHOP CHAIR FOR DETAILS ASAP EVEN IF YOU ARE NOT 100% SURE *** Other information is available on the workshop web site: - Workshop program (http://www.iro.umontreal.ca/~sfp2010/program.html) - Travel, accommodation and tourism information (http://www.iro.umontreal.ca/~sfp2010/travel.html) - Online registration (http://www.iro.umontreal.ca/~sfp2010/registration.html) Marc Feeley Scheme Workshop Chair feeley at iro.umontreal.ca

1 0

Small patch for compilation with the iOS SDK 4.0
by Alex Queiroz 16 Jul '10

16 Jul '10

Hallo, In the iOS SDK 4.0 the function stat64 exists but the struct stat64 does not (the stat64 function is marked as deprecated since stat always uses 64 bits). The attached patch looks for this struct, only enabling stat64 if both the function and the struct are found. Cheers, -- -alex http://www.artisancoder.com/

2 1

Compilation problem; only one of two object files can be loaded
by Per Eckerdal 10 Jul '10

10 Jul '10

I'm compiling scheme to C, then C to .o then linking, in separate steps. The goal is to create a dynamically loadable object file (one that can be loaded by Gambit's load procedure). I have this really odd problem: I have two dynamically loadable object files that are identical except for their names (so they are not byte-to-byte identical because the file names are embedded in the files). When I load one of them, it works, but when the other one is loaded, I get "Unknown error". This happens regardless of in which order I load them: $ gsc Gambit v4.6.0 > (load "test.o1") "/Users/per/prog/gambit/blackhole/test.o1" > (load "test.o2") *** ERROR IN (console)(a)2.1 -- Unknown error (load "test.o2") 1> *** EOF again to exit $ gsc Gambit v4.6.0 > (load "test.o2") "/Users/per/prog/gambit/blackhole/test.o2" > (load "test.o1") *** ERROR IN (console)(a)2.1 -- Unknown error (load "test.o1") 1> My guess is that I use incorrect compiler and/or linker flags somewhere. I had a similar issue where an object file was only loadable by the same gsc process that created it, which was because I didn't send "-D___DYNAMIC" to the C preprocessor. The files are compiled using the exact same process, I copy-paste the commands that are used to invoke GCC at the end of the mail. Any pointers? thanks, /Per The compilation and linking commands, for the two modules: (this is on OSX) gcc -no-cpp-precomp -Wno-unused -O1 -fno-math-errno -fschedule-insns2 -fno-trapping-math -fno-strict-aliasing -fwrapv -fomit-frame-pointer -fPIC -fno-common -mieee-fp -I"/usr/local/Gambit-C/include" -c -o "/Users/per/prog/gambit/github-modules/work/compile-tmp/1/test-rt.o" -D___DYNAMIC test-rt.c gcc -no-cpp-precomp -Wno-unused -O1 -fno-math-errno -fschedule-insns2 -fno-trapping-math -fno-strict-aliasing -fwrapv -fomit-frame-pointer -fPIC -fno-common -mieee-fp -I"/usr/local/Gambit-C/include" -c -o "/Users/per/prog/gambit/github-modules/work/compile-tmp/1/test-ct.o" -D___DYNAMIC test-ct.c gcc -no-cpp-precomp -Wno-unused -O1 -fno-math-errno -fschedule-insns2 -fno-trapping-math -fno-strict-aliasing -fwrapv -fomit-frame-pointer -fPIC -fno-common -mieee-fp -I"/usr/local/Gambit-C/include" -c -o "/Users/per/prog/gambit/github-modules/work/compile-tmp/1/test-vt.o" -D___DYNAMIC test-vt.c gcc -no-cpp-precomp -Wno-unused -O1 -fno-math-errno -fschedule-insns2 -fno-trapping-math -fno-strict-aliasing -fwrapv -fomit-frame-pointer -fPIC -fno-common -mieee-fp -I"/usr/local/Gambit-C/include" -c -o "/Users/per/prog/gambit/github-modules/work/compile-tmp/1/test-mi.o" -D___DYNAMIC test-mi.c gcc -no-cpp-precomp -Wno-unused -O1 -fno-math-errno -fschedule-insns2 -fno-trapping-math -fno-strict-aliasing -fwrapv -fomit-frame-pointer -fPIC -fno-common -mieee-fp -I"/usr/local/Gambit-C/include" -c -o "/Users/per/prog/gambit/github-modules/work/compile-tmp/1/test.o1.o" -D___DYNAMIC test.o1.c gcc -bundle -no-cpp-precomp -Wno-unused -O1 -fno-math-errno -fschedule-insns2 -fno-trapping-math -fno-strict-aliasing -fwrapv -fomit-frame-pointer -fPIC -fno-common -mieee-fp -flat_namespace -undefined suppress -D___DYNAMIC -I"/usr/local/Gambit-C/include" -o "/Users/per/prog/gambit/blackhole/src/test.o1" ../../github-modules/work/compile-tmp/1/test.o1.o ../../github-modules/work/compile-tmp/1/test-rt.o ../../github-modules/work/compile-tmp/1/test-ct.o ../../github-modules/work/compile-tmp/1/test-vt.o ../../github-modules/work/compile-tmp/1/test-mi.o gcc -no-cpp-precomp -Wno-unused -O1 -fno-math-errno -fschedule-insns2 -fno-trapping-math -fno-strict-aliasing -fwrapv -fomit-frame-pointer -fPIC -fno-common -mieee-fp -I"/usr/local/Gambit-C/include" -c -o "/Users/per/prog/gambit/github-modules/work/compile-tmp/1/test-rt.o" -D___DYNAMIC test-rt.c gcc -no-cpp-precomp -Wno-unused -O1 -fno-math-errno -fschedule-insns2 -fno-trapping-math -fno-strict-aliasing -fwrapv -fomit-frame-pointer -fPIC -fno-common -mieee-fp -I"/usr/local/Gambit-C/include" -c -o "/Users/per/prog/gambit/github-modules/work/compile-tmp/1/test-ct.o" -D___DYNAMIC test-ct.c gcc -no-cpp-precomp -Wno-unused -O1 -fno-math-errno -fschedule-insns2 -fno-trapping-math -fno-strict-aliasing -fwrapv -fomit-frame-pointer -fPIC -fno-common -mieee-fp -I"/usr/local/Gambit-C/include" -c -o "/Users/per/prog/gambit/github-modules/work/compile-tmp/1/test-vt.o" -D___DYNAMIC test-vt.c gcc -no-cpp-precomp -Wno-unused -O1 -fno-math-errno -fschedule-insns2 -fno-trapping-math -fno-strict-aliasing -fwrapv -fomit-frame-pointer -fPIC -fno-common -mieee-fp -I"/usr/local/Gambit-C/include" -c -o "/Users/per/prog/gambit/github-modules/work/compile-tmp/1/test-mi.o" -D___DYNAMIC test-mi.c gcc -no-cpp-precomp -Wno-unused -O1 -fno-math-errno -fschedule-insns2 -fno-trapping-math -fno-strict-aliasing -fwrapv -fomit-frame-pointer -fPIC -fno-common -mieee-fp -I"/usr/local/Gambit-C/include" -c -o "/Users/per/prog/gambit/github-modules/work/compile-tmp/1/test.o2.o" -D___DYNAMIC test.o2.c gcc -bundle -no-cpp-precomp -Wno-unused -O1 -fno-math-errno -fschedule-insns2 -fno-trapping-math -fno-strict-aliasing -fwrapv -fomit-frame-pointer -fPIC -fno-common -mieee-fp -flat_namespace -undefined suppress -D___DYNAMIC -I"/usr/local/Gambit-C/include" -o "/Users/per/prog/gambit/blackhole/src/test.o2" ../../github-modules/work/compile-tmp/1/test.o2.o ../../github-modules/work/compile-tmp/1/test-rt.o ../../github-modules/work/compile-tmp/1/test-ct.o ../../github-modules/work/compile-tmp/1/test-vt.o ../../github-modules/work/compile-tmp/1/test-mi.o

3 4

3nd CFPapers en 1st CFPart: 22nd Symposium on Implementation and Application of Functional Languages.
by jur 02 Jul '10

02 Jul '10

3RD CALL FOR PAPERS and 1ST CALL FOR PARTICIPATION 22nd Symposium on Implementation and Application of Functional Languages (IFL 2010) September 1-3, 2010 Utrecht University Alphen aan den Rijn, The Netherlands http://www.cs.uu.nl/ifl2010 ******************************************************************************************* ** Submission and Registration are now both OPEN ** ** If you intend to participate in IFL 2010, help us by registering as soon as possible. ** ** ** ** Submission closes July 25, Registration closes August 1 ** ******************************************************************************************* After a first successful visit to the USA, the Symposium on Implementation and Application of Functional Languages returns to Europe for its 22nd edition. The hosting institution is Utrecht University in the Netherlands, although the conference itself will take place in the ornithological theme park Avifauna in Alphen aan den Rijn, situated conveniently close to Schiphol (Amsterdam Airport). The symposium dates are September 1-3, 2010. The goal of the IFL symposia is to bring together researchers actively engaged in the implementation and application of functional and function-based programming languages. IFL 2010 will be a venue for researchers to present and discuss new ideas and concepts, work in progress, and publication-ripe results related to the implementation and application of functional languages and function-based programming. Following the IFL tradition, IFL 2010 will use a post-symposium review process to produce formal proceedings which will be published by Springer Verlag in the Lecture Notes in Computer Science series. All participants in IFL 2010 are invited to submit either a draft paper or an extended abstract describing work to be presented at the symposium. At no time may work submitted to IFL be simultaneously submitted to other venues. Here we follow the ACM Sigplan republication policy as defined on http://www.sigplan.org/republicationpolicy.htm. The submissions will be screened by the program committee chair to make sure they are within the scope of IFL, and will appear in the draft proceedings distributed at the symposium. Submissions appearing in the draft proceedings are not peer-reviewed publications. After the symposium, authors will be given the opportunity to incorporate the feedback from discussions at the symposium and will be invited to submit a revised full article for the formal review process. These revised submissions will be reviewed by the program committee using prevailing academic standards to select the best articles, which will appear in the formal proceedings. INVITED SPEAKER Johan Nordlander of Lulea University, the designer and developer of the Timber language, is the invited speaker at IFL 2010. Timber is a functional programming language that draws some of its concepts from object-oriented programming, and has built-in facilities for concurrent execution. The language is specifically targeted at implementing real-time embedded systems. TOPICS IFL welcomes submissions describing practical and theoretical work as well as submissions describing applications and tools. If you are not sure that your work is appropriate for IFL 2010, please contact the PC chair at jur(a)cs.uu.nl. Topics of interest include, but are not limited to: language concepts type checking contracts compilation techniques staged compilation runtime function specialization runtime code generation partial evaluation (abstract) interpretation generic programming techniques automatic program generation array processing concurrent/parallel programming concurrent/parallel program execution functional programming and embedded systems functional programming and web applications functional programming and security novel memory management techniques runtime profiling and performance measurements debugging and tracing virtual/abstract machine architectures validation and verification of functional programs tools and programming techniques industrial applications of functional programming PAPER SUBMISSIONS Prospective authors are encouraged to submit papers or extended abstracts to be published in the draft proceedings and to present them at the symposium. All contributions must be written in English, conform to the Springer-Verlag LNCS series format and not exceed 16 pages. The draft proceedings will appear as a technical report of the Department of Computer Science of Utrecht University. SPONSORS IFL 2010 is sponsored by Microsoft Research. As a result we can offer decreased participation fees for Master students and PhD students who plan to attend or present at IFL 2010. PETER LANDIN PRIZE The Peter Landin Prize is awarded to the best paper presented at the symposium every year. The honored article is selected by the program committee based on the submissions received for the formal review process. The prize carries a cash award equivalent to 150 Euros. IMPORTANT DATES Draft proceedings submission deadline July 25, 2010 Registration deadline August 1, 2010 IFL 2010 Symposium September 1-3, 2010 Submission for review process deadline October 25, 2010 Notification Accept/Reject December 22, 2010 Camera ready version February 17, 2011 PROGRAM COMMITTEE Jost Berthold University of Copenhagen (DIKU), Denmark Olaf Chitil University of Kent, UK John Clements California Polytechnic State University, USA Matthew Fluet Rochester Institute of Technology, USA Andy Gill Kansas University, USA Jurriaan Hage (Chair) University of Utrecht, Netherlands Bastiaan Heeren Open University, Netherlands Ralf Hinze University of Oxford, UK John Hughes Chalmers University of Technology, Sweden Yukiyoshi Kameyama University of Tsukuba, Japan Gabriele Keller University of New South Wales, Australia Pieter Koopman Radboud University Nijmegen, Netherlands Luc Maranget INRIA, France Simon Marlow Microsoft Research, UK Marco T. Morazán Seton Hall University, USA Rex Page University of Oklahoma, USA Ricardo Peña Universidad Complutense de Madrid, Spain Sven-Bodo Scholz University of Hertfordshire, UK Tom Schrijvers Catholic University of Leuven, Belgium Don Stewart Galois, USA Wouter Swierstra Vector Fabrics, Netherlands Don Syme Microsoft, UK Peter Thiemann University of Freiburg, Germany Phil Trinder Heriott-Watt University, Scotland Janis Voigtländer University of Bonn, Germany Viktória Zsók Eötvös Loránd University, Hungary

1 0

[ANN] REVISED DEADLINE for Scheme and Functional Programming Workshop
by Marc Feeley 14 Jui '10

14 Jui '10

Please note that the deadline for submitting papers to the Scheme workshop has been extended to Wednesday the 16th of June. The workshop website at http://www.iro.umontreal.ca/~sfp2010 gives more details on the submission process and workshop. Marc Feeley -------------------------------------------------------------------------- Call for Papers 2010 Workshop on Scheme and Functional Programming Montréal, Québec, Canada Saturday and Sunday August 21-22, 2010 http://www.iro.umontreal.ca/~sfp2010 Important Dates --------------- Submission: 16 June 2010 *** EXTENDED DEADLINE *** Notification: 4 July 2010 Final papers due: 23 July 2010 All deadlines are at 23:59 UTC (7:59 PM EDT, 6:59 PM CDT, 5:59 PM MDT, and 4:59 PM PDT). Scope ----- The 2010 Workshop on Scheme and Functional Programming is a forum for discussing experience with and future development of the Scheme programming language. Papers are invited concerning all aspects of the design, implementation, theory, and application of Scheme. Some example areas include (but are not limited to): - History, evolution and standardization of Scheme - Applications, experience and industrial uses of Scheme - Program-development environments, debugging, testing - Implementation (interpreters, compilers, tools, benchmarks, etc) - Distributed computing, concurrency, parallelism - Interoperability with other languages, FFIs - Continuations, macros, modules, object systems, types - Theory, formal semantics, correctness - Education - Scheme pearls (elegant, instructive uses of Scheme) There are two classes of submissions, regular papers (up to 12 pages) and short papers (around 6 pages). A Scheme pearl submission is a special category, and should be a short paper presenting an algorithm, idea or programming device using Scheme in a way that is particularly elegant. Following the model of earlier workshops, Scheme pearls and experience papers need not necessarily report original research results; they may instead report practical experience that will be useful to others, re-usable programming idioms, or elegant new ways of approaching a problem. The key criterion for such a paper is that it makes a contribution from which other practitioners can benefit. It is not enough simply to describe a program! The proceedings of the conference will be published as a Université de Montréal technical report. Instructions for authors ------------------------ Authors should submit a 100-200 word abstract and a full paper by the end of Wednesday, 16 June 2010, Universal Coordinated Time. (The end of the day UTC corresponds to 23:59 UTC, 7:59 PM EDT, 6:59 PM CDT, 5:59 PM MDT, and 4:59 PM PDT.) Papers must be submitted in PDF format, or as PostScript documents that are interpretable by Ghostscript, and they must be printable on US Letter sized paper. Suitable style files for LaTeX: - class file http://www.iro.umontreal.ca/~sfp2010/sigplanconf.cls - style guide http://www.iro.umontreal.ca/~sfp2010/sigplanconf-guide.pdf - template http://www.iro.umontreal.ca/~sfp2010/sigplanconf-template.tex - sample paper http://www.iro.umontreal.ca/~sfp2010/retrospective.tex - sample references http://www.iro.umontreal.ca/~sfp2010/retrospective.bbl Submissions will be carried out electronically via the Web, at http://www.iro.umontreal.ca/~sfp2010/submit.html A submission will be evaluated according to its relevance, correctness, significance, originality, and clarity. It should explain its contributions in both general and technical terms, clearly identifying what has been accomplished, explaining why it is significant, and comparing it with previous work. The technical content should be accessible to a broad audience. There are two classes of submissions, regular papers and short papers: Regular papers -------------- Submissions should be no more than 12 pages (including bibliography and appendices) in standard ACM conference format: two columns, nine point font on ten point baseline, page 20pc (3.33in) wide and 54pc (9in) tall with a column gutter of 2pc (0.33in). Authors wishing to supply additional material to the reviewers beyond the 12 page limit can do so in clearly marked appendices, on the understanding that reviewers may not read the appendices. Submissions that do not meet these guidelines will not be considered. Short papers ------------ Short papers need not present novel research; it is sufficient that they present material of interest or utility to the Scheme or functional-programming community. Scheme pearls submissions should be presented as short papers. Short papers should be formatted with the same guidelines as regular papers, but are expected to be around six pages in length. Organization ------------ Conference Chair and Program Chair - Marc Feeley, Université de Montréal Program Committee - Alan Bawden, independent consultant - Olivier Danvy, Aarhus University - Christopher Dutchyn, University of Saskatchewan - Felix S. Klock II, Northeastern University - Jay McCarthy, Brigham Young University - Scott McKay, ITA software Steering Committee - William D. Clinger, Northeastern University - Marc Feeley, Université de Montréal - Robby Findler, University of Chicago - Dan Friedman, Indiana University - Christian Queinnec, University Paris 6 - Manuel Serrano, INRIA Sophia Antipolis - Olin Shivers, Northeastern University - Mitchell Wand, Northeastern University

1 0

##car ##cdr ##null?
by Álvaro Castro-Castilla 11 Jui '10

11 Jui '10

Hi, I can see sometimes these kind of procedures ##car, ##cdr, ##null? etc... in code that has been optimized for Gambit. What is exactly the difference between those and the standard ones? And if these ones are faster, why are they defined as separate functions instead of just substituting the standard ones when in (unsafe) compilation? Then, how are they really used? Thanks a lot, Álvaro

4 6