Août 2016 - Gambit-list - mailman.iro.umontreal.ca

{Spam?}
by Avi nash 05 Aoû '16

05 Aoû '16

jerry05(a)live.com

1 0

Re: [gambit-list] Gambit version for medical apps?
by Adam 02 Aoû '16

02 Aoû '16

2016-07-30 20:38 GMT+08:00 Marc Feeley <dr.marc.feeley(a)gmail.com>: > The first order of business is choosing which version(s) of Gambit to > branch from. It could be more than one version if various groups or > individuals have different requirements. I foresee that the maintenance of > these branches will be driven by these groups, so there is no reason to > place a limit of 1. However, for the sake of focus, we should probably not > maintain more than 2 or 3 “stable” branches in the long run and I think we > should start with one branch to see how it goes. > Yes! So lets first determine which branch to start from… v4.7.0 or v4.7.2 or > other? > > Also how should we name the branches… I propose “v4.7.0-stable” > If you have a particular motivation for 4.7.0 then go with it. I guess people suggested 4.7.2 simply because it was slightly newer, I would guess it has some new features. Though perhaps 4.7.0 is a milestone so sure then go with it. James, Mattias, Brad, anyone else, any thoughts? I guess spend no more time than until Thu or Fri to wait for this, the difference is insignificantly small.

2 1

Need review for an open-source book/library on Computation at Compile Time (using Gambit)
by Bill Six 01 Aoû '16

01 Aoû '16

Marc, et al., I'm finishing writing an open-source book/library on Computation at Compile Time, using Gambit. Before I self-publish it, I would like feedback. The book is about augmenting the compiler with the code which it is compiling, thus treating the compiler as an interpreter. Testing dominates the compile-time computation, as each procedure in the book is collocated with tests for that procedure. Should any test fail, the library does not get built. Sound interesting? The code is at https://github.com/billsix/bug, but I will send my current PDF on request. Bill Six

3 4

Error compiling macros
by ochi n 01 Aoû '16

01 Aoû '16

Hi all, I'm trying to compile a simple program using macros but for some reason it won't work. This is the code in test.scm (define-syntax while (syntax-rules () ((while condition body ...) (let loop () (if condition (begin body ... (loop)) #f))))) (define x 0) (while (< x 5) (set! x (+ x 1)) (print x)) When I load the file into the interpreter (with the -:s option) it works, but when I try to compile it (using gambitc -:s -exe test.scm) I get the following error: *** ERROR -- missing or invalid linking information for module "/usr/lib/gambit-c/_gambit" /usr/lib/gcc/x86_64-pc-linux-gnu/6.1.1/../../../../lib/crt1.o: In function `_start': (.text+0x20): undefined reference to `main' test.o: In function `___setup_mod': test.c:(.text+0xa): undefined reference to `___G__20_test' test.o: In function `___init_mod': test.c:(.text+0x26): undefined reference to `___G__20_test' test.o: In function `___H__20_test': test.c:(.text+0x113): undefined reference to `___G__24_sc_2d_put_2d_cte' test.c:(.text+0x181): undefined reference to `___G__24_sc_2d_put_2d_cte' test.c:(.text+0x1a2): undefined reference to `___G__24_sc_2d_put_2d_cte' test.c:(.text+0x1f3): undefined reference to `___G__24_sc_2d_put_2d_cte' test.c:(.text+0x214): undefined reference to `___G_x' test.c:(.text+0x24d): undefined reference to `___G_x' test.c:(.text+0x3a6): undefined reference to `___G_x' test.c:(.text+0x450): undefined reference to `___G_x' test.c:(.text+0x59b): undefined reference to `___G__24_syntax_2d_dispatch' test.c:(.text+0x60f): undefined reference to `___G__24_syntax_2d_dispatch' test.c:(.text+0x6a0): undefined reference to `___G_syntax_2d_error' test.c:(.text+0x6fa): undefined reference to `___G_syntax_2d_error' test.o: In function `____20_test': test.c:(.text+0xd38): undefined reference to `___S__2a_top_2a_' test.c:(.text+0xd46): undefined reference to `___S_any' test.c:(.text+0xd62): undefined reference to `___S_body' test.c:(.text+0xd70): undefined reference to `___S_condition' test.c:(.text+0xd8c): undefined reference to `___S_each_2d_any' test.c:(.text+0xd9a): undefined reference to `___S_global' test.c:(.text+0xdc4): undefined reference to `___S_loop' test.c:(.text+0xdd2): undefined reference to `___S_ribcage' test.c:(.text+0xdee): undefined reference to `___S_syntax_2d_object' test.c:(.text+0xe18): undefined reference to `___S_top_2d_ribcage' test.c:(.text+0xe34): undefined reference to `___S_x' collect2: error: ld returned 1 exit status I tried compiling with the interactive mode using (compile-file-to-target "test.scm") (quit) gambitc -exe test.c and it compiles well, but when I try to run the exe I get: *** ERROR IN | test| -- Operator is not a PROCEDURE (#!unbound '#(syntax-object while ((top) #(ribcage #(while) #((top)) #(while)))) '#<procedure #2> '*top*) No matter how hard I try I can't compile any code that makes use of macros. Any help appreciated! (I'm using Arch Linux and I installed gambit from Arch's repositroy, everything else apart from macros works well)

2 5

Gambit version for medical apps?
by Gorges, Matthias 01 Aoû '16

01 Aoû '16

Greetings, I have a question for the community in general, and Marc in particular. As some of you may know the Pediatric Anesthesia Research team at UBC uses Gambit as part of their LambdaNative framework (http://www.lambdanative.org/) to develop medical software. Some of our applications are mission and safety critical as they control drug delivery to patients (doi: 10.1145/2635648.2635651), or provide decision support during triage of pregnant women by community health workers (doi: 10.1109/JBHI.2014.2301156). Hence, we are trying to identify which version of Gambit to use, with the main deciding factor being reliability and stability. While the main LambdaNative branch uses 4.7.9 - we are considering updating to 4.8.5 once we figure out how to integrated the revised tracing into our exception handler/logger, we use much older versions for our production-quality applications: Specifically, we use 4.7.2 for our mobile Android apps, as there were issues with both the ##thread-heartbeat! and other hard-to-reproduce crashes in very large Android apps with later Gambit versions. For our closed-loop system on Linux we reverted back even further at 4.7.0. Here, our attempt to update to 4.7.9 resulted in weeks of debugging after the application segfaulted during clinical pilot testing, having passed weeks of both manual and automated system tests in the lab. Unfortunately, we were never to identify the exact crash location, but all we could show was that the crash did not originate from our (user-level) code but the Gambit infrastructure code. I appreciate that the project's current goals are more along the line of making a more universal output language processor, which is a laudable endeavor e.g. for improved in-browser support. However, I would appreciate some guidance in helping us chose a "stable" version without potentially wasting man-months in testing (and failing) to identify such a version ourselves. Many Thanks, Matthias

6 25