/bin/sh
## -*- mode: scheme; coding: utf-8 -*-
## Time-stamp: <2018-09-14 08:43:42 barry>
exec ${GUILE:-guile} -e main -s $0 ${1+"$@"}
!#
--
Barry Fishman
bin/sh")
In ice-9/eval.scm:
223:20 1 (proc #)
In unknown file:
0 (%resolve-variable (7 . #) #)
--8<---cut here---end--->8---
In the test code I see:
(primitive-load (getenv "DOC_GUILE_LIBRARY_SCM"))
And in the Makefile:
DOC_GUILE_LIBRARY_SCM=$(top_srcdir)/doc/guile-library.scm
And:
top_srcdir=..
so I don't know where the "/bin/sh" could be coming from.
--
Barry Fishman
tup.py or (even better) Haskell Cabal/Hackage. *Not*
something like Emacs packages.
--
Barry Fishman
evelopers might presume about an interface
rather a malicious act.
Although Scheme itself is not the usual place to think about complex
systems, I think Guile does, given what is currently being implemented.
--
Barry Fishman
resulting Makefiles seem to be far more complicated than
necessary for a guile module.
It seems that a general GNU configure environment based on Guile is
becoming increasingly remote as Guile moves from a simple to build
extension language to a complex multi-language environment, too far down
the build dependency chain to use.
--
Barry Fishman
or throwing code.
(define-method (my-message (err ))
(format #f "ERROR: Code ~S in ~S" (code err) (path err)))
(define-method (my-message (err ))
(format #f "ERROR: Unknown error type ~S" err))
--
Barry Fishman
