But I also want to make sure I'm pointnig gerbil at a version of gambit that its supposed to be with, rather than the one that is
Gambit/current
definitely its when you set
--bindir, --libdir, and --includedir to things other than the gambit HOME
(define (gambit-gsc-path)
(if gambit-prefix
(string-append gambit-prefix "/bin/gsc")
"gsc"))
("wrong" might be my mental model, but then I'm not sure I want to use it if the spec doesn't match said mental model)
package: "bug"
":" ; ( echo -e '\n\nINTERPRETED\n\n' ; gxi reordered.ss; echo -e '\n\nCOMPILED\n\n' ; gxc -O reordered.ss && gxi -e '(import :bug/reordered)' ) 2>&1 | less
(def (reordered)
(displayln 100)
(def x (begin (displayln 200) 42))
(displayln 300)
(displayln 400 [x])
(displayln 500)
(def y (begin (displayln 600) 23))
(displayln 700 [y]))
(reordered)
line 400 is moved until after lines 500 and 600.
Oh, there has to be some
set!'s involved doesn't there ....
drewc @drewc searches for /delete lol
drewc @drewc should likely read the spec before thinking out "loud"
drewc @drewc blames Amaretto which he misspelled :P
@lambdanon_twitter maybe you can package Gerbil for GUIX? You could use the Nix recipes as reference.
@lambdanon_twitter I have a personal guix channel with both gambit and gerbil (full) that I use. I could send you the build recipes when I get back home if you still need them.
(Sadly I don't have the files published yet)
if you do get around to posting them ping us here :)
I'm trying to write a library which may shadow some builtins and think I should use a namespace for it, but I'm not sure how
(import (rename-in :gerbil/gambit/os (current-time builtin-current-time)))
I was just about to get started on this, and then realized i better check if its already packaged for guix, and voila, its already there
@rvs314 "namespaces" are simply a prefix to the symbol. In other words, a symbol named "foo#bar" is known as "bar" in the "foo" namespace. Gambit has a way to specify "for these symbols, or all unbound symbols, use the namespace prefix when referencing that symbol". So, after READ but before EVAL, (bar "baz") becomes (foo#bar "baz").
try
gxc -staticor have a look in ~/.gerbil/lib/static/ to see the .scm files that Gerbil outputs to the Gambit compiler, as they are also the "step" between "namespaces" and "packages".
In other words, if the file is named "foo" and in the "baz" package, symbols will be defined in the "baz/foo" namespace
ie:
[drewc@nyx:/tmp]$ echo package: baz > foo.ss
[drewc@nyx:/tmp]$ echo "(def (foo bar) (cons bar 'baz))" >> foo.ss
[drewc@nyx:/tmp]$ gxc -static -d . -v ./foo.ss
compile ./foo.ss
compile baz/foo
compile ./baz/foo__0.scm
invoke gsc (gsc -:i8,f8,-8,t8 ./baz/foo__0.scm)
copy static module ./baz/foo__0.scm => ./static/baz__foo.scm
compile ./baz/foo__rt.scm
invoke gsc (gsc -:i8,f8,-8,t8 ./baz/foo__rt.scm)
compile ./baz/foo.ssi
[drewc@nyx:/tmp]$ ls static/
baz__foo.scm
[drewc@nyx:/tmp]$ cat static/baz__foo.scm
(declare (block) (standard-bindings) (extended-bindings))
(define baz/foo#foo (lambda (_bar388_) (cons _bar388_ 'baz)))
Now, as for "modules", there are so many different kinds with different formats and ways of dealing with them, BUT, assuming we are talking about basic Gerbil here lol, by default, ":baz/foo" also becomes the module name. So I can use that to tell Gerbil that this namespace and this module work in such a way that
import becomes a namespace reader.
ie:
# First add :baz/foo to the global library
[drewc@nyx:/tmp]$ gxc -static -v ./foo.ss
# [...]
compile ~/.gerbil/lib/baz/foo.ssi
[drewc@nyx:/tmp]$ echo package: baz > bar.ss
[drewc@nyx:/tmp]$ echo '(import (only-in :baz/foo foo))' >> bar.ss
[drewc@nyx:/tmp]$ echo '(def (qwerty uiop) (foo uiop))' >> bar.ss
[drewc@nyx:/tmp]$ gxc -static -d . -v -S ./bar.ss
#[...]
copy static module ./baz/bar__0.scm => ./static/baz__bar.scm
[drewc@nyx:/tmp]$ ls static/
baz__bar.scm baz__foo.scm
[drewc@nyx:/tmp]$ cat static/baz__bar.scm
(declare (block) (standard-bindings) (extended-bindings))
(define baz/bar#qwerty (lambda (_uiop388_) (baz/foo#foo _uiop388_)))
Also important to note is that the bar and uiop arguments became a gensym'd thingie. This avoids conflicts of course, and goes along with "symbols are not what they appear".
So an expander-module is basically Gerbil's way of saying "map this symbol to this namespace before expanding on it". We can actually change the namespace, and the package, a number of ways, but by default it is "<package>/<filename" that becomes the module name and the namespace.
Note: none of the symbols I typed ended up in the
.scm file. def => define, qwerty => baz/bar#qwerty, foo => baz/foo#foo, bar => _bar388_ and uiop => _uiop388_. So, while namespaces are certainly involved, I did not have to care about them in the least. Gerbil is a meta-dialect on top of ol' Scheme :P