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

leap seconds
by Faré 02 Jul '17

02 Jul '17

Dear Gambit list, I'm using Gambit on Unix, and I'd like to store some real time data with a date stamp. (current-time) seems appropriate, but I'm not sure I understand the treatment of leap seconds -- particularly leap seconds inserted. Is (current-time) output monotonic (assuming a monotonic system clock), or will the output go back in time during leap seconds? What are proper functions to extract a date from (current-time) ? Is it guaranteed to use the Unix Epoch when running on Linux? -#f

2 2

Arguments to conversion functions
by Vijay Mathew 28 Jui '17

28 Jui '17

Hi Marc, Could you please describe the parameters of the ___SCMOBJ_to_XXX macros? Especially, what is the significance of the third (arg_num) parameter? Thanks, --Vijay

2 1

Error configuring gambit source
by Vijay Mathew 28 Jui '17

28 Jui '17

Hi, I am trying to build the latest development source (gambit-v4_8_8-devel) on Mac OS X (darwin14.5.0). I am running into the following error while configuring the source: In file included from _num.c:705:0: _num.c: In function ‘long int ___H__20___num(___processor_state)’: ../include/gambit.h:2880:98: error: ‘__builtin_add_overflow’ was not declared in this scope #define ___FIXADDP(x,y)(___EXPECT_FALSE(__builtin_add_overflow((___WORD)(x),(___WORD)(y),&___temp))?___FAL:___temp) ^ ../include/gambit.h:4296:30: note: in definition of macro ‘___SET_R3’ #define ___SET_R3(val)___R3=(val); ^ ../include/gambit.h:2880:25: note: in expansion of macro ‘___EXPECT_FALSE’ #define ___FIXADDP(x,y)(___EXPECT_FALSE(__builtin_add_overflow((___WORD)(x),(___WORD)(y),&___temp))?___FAL:___temp) ^ _num.c:22107:14: note: in expansion of macro ‘___FIXADDP’ ___SET_R3(___FIXADDP(___R1,___R2)) ^ ../include/gambit.h:2890:95: error: ‘__builtin_mul_overflow’ was not declared in this scope #define ___FIXMULP(x,y)(___EXPECT_FALSE(__builtin_mul_overflow((___WORD)(x),___INT(y),&___temp))?___FAL:___temp) ^ ../include/gambit.h:4296:30: note: in definition of macro ‘___SET_R3’ #define ___SET_R3(val)___R3=(val); ^ ../include/gambit.h:2890:25: note: in expansion of macro ‘___EXPECT_FALSE’ #define ___FIXMULP(x,y)(___EXPECT_FALSE(__builtin_mul_overflow((___WORD)(x),___INT(y),&___temp))?___FAL:___temp) ^ _num.c:22698:14: note: in expansion of macro ‘___FIXMULP’ ___SET_R3(___FIXMULP(___R1,___R2)) ^ ../include/gambit.h:2907:98: error: ‘__builtin_sub_overflow’ was not declared in this scope #define ___FIXSUBP(x,y)(___EXPECT_FALSE(__builtin_sub_overflow((___WORD)(x),(___WORD)(y),&___temp))?___FAL:___temp) ^ ../include/gambit.h:4296:30: note: in definition of macro ‘___SET_R3’ #define ___SET_R3(val)___R3=(val); ^ ../include/gambit.h:2907:25: note: in expansion of macro ‘___EXPECT_FALSE’ #define ___FIXSUBP(x,y)(___EXPECT_FALSE(__builtin_sub_overflow((___WORD)(x),(___WORD)(y),&___temp))?___FAL:___temp) ^ _num.c:23679:14: note: in expansion of macro ‘___FIXSUBP’ ___SET_R3(___FIXSUBP(___R1,___R2)) ^ The complete configure command is: ./configure --enable-single-host --enable-multiple-threaded-vms --bindir=${MY_HOME}/platform/gsc/bin --includedir=${MY_HOME}/platform/gsc/include --libdir=${MY_HOME}/platform/gsc/lib If the `--enable-multiple-threaded-vms` option is removed, I get a different error: gcc -Wno-unused -Wno-write-strings -O1 -fwrapv -fno-strict-aliasing -fno-trapping-math -fno-math-errno -fschedule-insns2 -fomit-frame-pointer -fPIC -fno-common -mieee-fp -mpc64 -I"../include" -o "gsi" _gsi.o _gsi_.o "../lib/libgambit.a" libgambitgsi.a Undefined symbols for architecture x86_64: "___builtin_add_overflow", referenced from: ____H__20___num in libgambit.a(_num.o) ____H__20___system in libgambit.a(_system.o) "___builtin_mul_overflow", referenced from: ____H__20___num in libgambit.a(_num.o) "___builtin_sub_overflow", referenced from: ____H__20___num in libgambit.a(_num.o) ld: symbol(s) not found for architecture x86_64 What am I doing wrong? Thanks, --Vijay

3 7

Trying to compile gambit head on NixOS
by Faré 21 Jui '17

21 Jui '17

I tried to build gambit head on NixOS, and I have a weird error while trying to compile gsi: gcc -pthread -Wno-unused -Wno-write-strings -Wdisabled-optimization -O6 -fwrapv -fno-strict-aliasing -fno-trapping-math -fno-math-errno -fschedule-insns2 -fmodulo-sched -freschedule-modulo-scheduled-loops -fomit-frame-pointer -fPIC -fno-common -mpc64 -pthread -rdynamic -I"../include" -o "gsi" _gsi.o _gsi_.o "../lib/libgambit.so" -lutil -ldl -lm -L/usr/local/opt/openssl/lib -lssl -lcrypto libgambitgsi.so ../lib/libgambit.so: undefined reference to `___PAIRMUTABLEP' collect2: error: ld returned 1 exit status make[1]: *** [makefile:178: gsi] Error 1 make[1]: Leaving directory '/tmp/nix-build-gambit-4.8.6.drv-0/gambit-2c34b63/gsi' while trying to compile gsi Looking at the code, it looks like 81ffcaedb133e9cc8936db3e4d9ec85626497414 has stopped defining ___PAIRMUTABLEP, but that macro is still used in gsc/_asm.c and lib/_std.c that are included in libgambit.so, causing the failure. The modified pkgs/development/compilers/gambit/default.nix is as below: { stdenv, fetchurl, fetchgit, openssl }: stdenv.mkDerivation rec { name = "gambit-${version}"; version = "4.8.8-dev"; devver = "4_8_8_dev"; # src = fetchurl { # url = "http://www.iro.umontreal.ca/~gambit/download/gambit/v4.8/source/gambit-v${d…"; # sha256 = "0j3ka76cfb007rlcc3nv5p1s6vh31cwp87hwwabawf16vs1jb7bl"; # }; src = fetchgit { url = "https://github.com/feeley/gambit.git"; rev = "2c34b6328ce508cd0277c7dfddbab3f698b785c5"; sha256 = "1is5f5b4k18rr3k3nzhb7wny9h68kj509miizsqxblrdmvzkf1ic"; }; configureFlags = [ "--enable-single-host" "--enable-shared" "--enable-absolute-shared-libs" "--enable-c-opt=-O6" "--enable-gcc-opts" "--enable-inline-jumps" "--enable-thread-system=posix" "--enable-dynamic-tls" "--enable-openssl" ]; buildInputs = [ openssl ]; meta = { description = "Optimizing Scheme to C compiler"; homepage = "http://gambitscheme.org"; license = stdenv.lib.licenses.lgpl2; platforms = stdenv.lib.platforms.linux; maintainers = with stdenv.lib.maintainers; [ thoughtpolice raskin ]; }; } —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Gauss, when asked how soon he expected to reach certain mathematical conclusions, replied that he had reached them long ago, all he was worrying about was how to reach them! [Karl F. Gauss (1777-1855), German mathematician]

2 1

r/scheme: I developed a medium sized, cross platform strategy/roguelike game in ~100% Scheme. Here is a summary of my experience:
by Bradley Lucier 16 Jui '17

16 Jui '17

https://www.reddit.com/r/scheme/comments/6hng3q/i_developed_a_medium_sized_… Vincent Toups (http://procyonic.org/) has written a new game using LambdaNative and Gambit. Interesting discussion, including need for libraries, etc. Brad

1 0

1st CfP: IFL 2017 (29th Symposium on Implementation and Application of Functional Languages)
by publicityifl＠gmail.com 12 Jui '17

12 Jui '17

<div dir="ltr">Hello, Please, find below the first call for papers for IFL 2017. Please forward these to anyone you think may be interested. Apologies for any duplicates you may receive. best regards, Jurriaan Hage Publicity Chair of IFL --- IFL 2017 - CALL FOR PAPERS ========================== 29th SYMPOSIUM ON IMPLEMENTATION AND APPLICATION OF FUNCTIONAL LANGUAGES ======================================================================== University of Bristol, UK In cooperation with ACM SIGPLAN Wednesday 30 August - Friday 1 September, 2017 <a href="http://iflconference.org/">http://iflconference.org/</a> Scope ----- 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 2017 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. Peer-review ----------- Following the IFL tradition, IFL 2017 will use a post-symposium review process to produce the formal proceedings. All participants of IFL 2017 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; submissions must adhere to ACM SIGPLAN's republication policy: <a href="http://www.sigplan.org/Resources/Policies/Republication">http://www.sigplan.org/Resources/Policies/Republication</a> 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. Hence, publications that appear only in the draft proceedings are not subject to the ACM SIGPLAN republication policy. 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. From the revised submissions, the program committee will select papers for the formal proceedings considering their correctness, novelty, originality, relevance, significance, and clarity. The formal proceedings will appear in the International Conference Proceedings Series of the ACM Digital Library. Important dates --------------- Mon 31 July 2017 : Submission deadline draft papers Wed 2 August 2017 : Notification of acceptance for presentation Fri 4 August 2017 : Early registration deadline Fri 11 August 2017 : Late registration deadline Mon 21 August 2017 : Submission deadline for pre-symposium proceedings Wed 30 August 2017 - Fri 1 September 2017 : IFL Symposium Mon 4 December 2017 : Submission deadline for post-symposium proceedings Wed 31 January 2018 : Notification of acceptance for post-symposium proceedings Mon 12 March 2018 : Camera-ready version for post-symposium proceedings Submission details ------------------ 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. Papers must use the new ACM two columns conference format, which can be found at: <a href="http://www.acm.org/publications/proceedings-template">http://www.acm.org/publications/proceedings-template</a> For the pre-symposium proceedings we adopt a 'weak' page limit of 12 pages. For the post-symposium proceedings the page limit of 12 pages is firm. Authors submit through EasyChair: <a href="https://easychair.org/conferences/?conf=ifl2017">https://easychair.org/conferences/?conf=ifl2017</a> Topics ------ IFL welcomes submissions describing practical and theoretical work as well as submissions describing applications and tools in the context of functional programming. If you are not sure whether your work is appropriate for IFL 2017, please contact the PC chair at <a href="mailto:nicolas.wu@bristol.ac.uk">nicolas.wu(a)bristol.ac.uk</a>. Topics of interest include, but are not limited to: - language concepts - type systems, type checking, type inferencing - compilation techniques - staged compilation - run-time function specialization - run-time code generation - partial evaluation - (abstract) interpretation - metaprogramming - generic programming - automatic program generation - array processing - concurrent/parallel programming - concurrent/parallel program execution - embedded systems - web applications - (embedded) domain specific languages - security - novel memory management techniques - run-time profiling performance measurements - debugging and tracing - virtual/abstract machine architectures - validation, verification of functional programs - tools and programming techniques - (industrial) applications 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. Programme committee ------------------- Chair: Nicolas Wu, University of Bristol, UK - Kenichi Asai, Ochanomizu University, Japan - Sandrine Blazy, University of Rennes 1, France - Carlos Camarao, Universidade Federal de Minas Gerais, Brazil - Stephen Dolan, University of Cambridge, UK - Jurriaan Hage, Utrecht University, Netherlands - Yukiyoshi Kameyama, University of Tsukuba, Japan - Benjamin Lerner, Brown University, USA - Bas Lijnse, Radboud University, Netherlands - Garrett Morris, University of Kansas, USA - Miguel Pagano, Universidad Nacional de C√≥rdoba, Argentina - Tomas Petricek, Alan Turing Institute, UK - Maciej Pir√≥g, University of Wroc≈Çaw, Poland - Exequiel Rivas, Universidad Nacional de Rosario, Argentina - Neil Sculthorpe, Nottingham Trent University, UK - Melinda T√≥th, E√∂tv√∂s Lor√°nd University, Hungary - Phil Trinder, Glasgow University, UK - Kanae Tsushima, National Institute of Informatics, Japan - Marcos Viera, Universidad de la Republica, Uruguay - Meng Wang, University of Kent, UK Venue ----- The IFL 2017 will be held in association with the Department of Computer Science, University of Bristol, UK. Bristol is located in South West England, and can be easily reached from Bristol Airport. See the website for more information on the venue. </div>  <a style='display: block; margin: 32px 0 40px 0; padding: 10px; font-size: 1em; text-align: center; border: 0; border-top: 1px solid gray; ' href='https://goo.gl/2ksdRv'>powered by GSM. Free mail merge and email marketing software for Gmail.</a>

1 0

A weak-reference box object possible?
by Adam 11 Jui '17

11 Jui '17

Hi Marc, I realize that Gambit delivers weak references only through hashtables and will objects. I suspect a weakly referenced box, i.e. a will object without action, would be useful. Do will objects have any overhead due to the action.. I would guess so, or is it so small that users implementing a weakly referenced box themselves by (define (make-weak-box v) (make-will v (lambda (v) #!void))), would always be a clean solution? I recall that will objects take extra time during some GC phase, actually extend the STW, so that's part why I wanted to ask this question. Also I brought this up as the absence of a "simple" weak reference box object appeared a bit assymetric to me, e.g., what about the cases where you want an object reference but want it to be weak, and are fine with it becoming #!void or #f or #!undefined or alike when collected. Any comments would be much welcome. Thanks!

1 0

Force in --enable-auto-forcing not replacing slot with forced value, possible?
by Adam 11 Jui '17

11 Jui '17

Hi Marc, I notice that in --enable-auto-forcing, doing (begin (define x (delay 1)) (+ a)), a still shows as a promise object in the REPL, and (##promise? a) evaluates to #t (even while as expected, the force is automatic so (+ a) evaluates to 1 etc.). I had an impression that auto forcing was implemented through something like a read barrier, which would replace the slot containing the promise object, with the forced value. This is not so currently. This means a memory access indirection remains at each access of a promise value, right? Would it be trivial to implement such replacement as to remove that indirection? Thanks!

1 0

Size of the universal libraries (eg. lib/_gambit.php)
by Ben 09 Jui '17

09 Jui '17

hi, After a long pause I try to have another look into Gambits universal backend. In the end I'd like to write small article on my website about it, so I made some efforts to understand how it works. Some observations: 1. AFAIK you have to cat 3 files code.php (compiled) code_.php (linked) and lib/_gambit.php (precompiled) into a standalone script. The step where you compile to code.php (gsc -:=. -target php code.scm) gives me a code.o1 file. Is this a bug? 2. The precompiled library (_gambit.php) is 15 Mb of size. So the first thing I've tried to do is to reduce the size of this file. Therefor I've built an analyzer tool which should have removed all supposedly dead code in _gambit.php. The problem is: there are no function calls neither from code.php nor from code_.php into _gambit.php. So I wonder is _gambit.php actually a virtual machine, where functions are called dynamically with the help of a big global symbol table? I'm a bit in the dark here... Thanks for some clarifications. Regards Ben

3 2

Gerbil v0.11 -- MySQL, LevelDB, and more
by Dimitris Vyzovitis 05 Jui '17

05 Jui '17

A busy new release of Gerbil, which rounds up the :std/db package with support for MySQL and LevelDB, adds a command line argument parsing library, and a host of other improvements small and big. There is also new documentation: - The `:std/db` package has been documented in the Guide: https://github.com/vyzo/gerbil/blob/master/doc/guide.md#databases - A new tutorial illustrates the very basics of distributed prgramming in Gerbil and LMDB: https://github.com/vyzo/gerbil/blob/master/doc/tutorial/kvstore.md As usual, for sources and downloads: https://github.com/vyzo/gerbil https://github.com/vyzo/gerbil/releases For questions and support, come say hi on #gerbil-scheme in irc.freenode.net . Detailed Changes for v0.11: - stdlib: - std/db - std/db/mysql: MySQL dbi interface with FFI driver [new] - std/db/leveldb: LevelDB interface with FFI driver [new] - std/db/conpool: connection pools for SQL databases [new] - std/db/dbi: reset statements after exec and query evaluation - std/db/sqlite: Fix SMP-safety on FFI (removes ffi_last_error) - std/getopt: command line argument parsing library [new] - std/misc/ports: port utilites (copy-port) [new] - std/sugar: while and until macros - std/iter: add iter-fini! to iteration protocol for stateful iterator cleanup - std/make: - track preludes in make-depgraph - use build-specs for depgraph generation with make-depgraph/spec - check library dependencies on build decisions - std/actor: final structs for messages - r7rs: - scheme/base: [gambiteer] implement exact-integer-sqrt - prelude: - gerbil/core - add u8vector primitives to <host-runtime> - eval is there - syntax/loc macro from Racket - gerbil/gambit: - gerbil/gambit/bytes: refactored synonyms for u8vector ops [new] - expander: - bind core features at root context, including system-type features - strict refernces for positive phis - compiler: - update exe stubs to hook display-exception - runtime: - clean up confusing direct-* MOP functions - doc: - guide.md#databases: document the :std/db package [new] - tutorial/kvstore.md: a key-value store server tutorial [new] Happy Hacking! -- vyzo

1 0