> as already discussed briefly with the Guile guys behind the new VM thing,
> I got the idea to implement Emacs Lisp as supported language for the Guile
> VM system.
I won't have time to mentor it, but I'd like to point out some relevant
directions in Emacs's future: as some of you know, other tha
> ... And notice how the syntax in that message isn't even close to valid Agda!
That is unfair: I copied the type annotations from random places in the
Agda library (and then edited them to make them more interesting).
Stefan
PS: Of course, any sequence of chars (especially funny Unico
> - "Create a symbolic link named @var{oldpath} with the value\n"
> - "(i.e., pointing to) @var{newpath}. The return value is\n"
> + "Create a symbolic link named @var{newpath} with the value\n"
> + "(i.e., pointing to) @var{oldpath}. The return value is\n"
This i
> To compress even further we need a way to could use
> x ->[SCM/2/SCM/2], witt SCM/2 the same tagging half the size as the normal
Note that this is not specific to cons-cells. I've been meaning to try
and experiment with such a box-compression scheme for several years, but
it never got high enou
>____
> Objects in | | | |
> GC-managed | SMOB 1 | | SMOB 2 |
> heap |__| |__|
> | ^
> The original GOOPS implementation had a somewhat crazy feature that an
> application of a generic function to a specific argument list first
> resulted in the standard MOP procedure for finding a set of applicable
> methods and, second, from this/these generated something called a "cmethod"
> (co
> (define (map f l)
> (if (pair? l)
> (cons (f (car l))
> (map f (cdr l)))
> '()))
>
> whereas we used to have to write code like this in order to support long
> lists without overflowing the stack:
>
> (define (map f l)
> (let loop ((l l) (out '()))
>
> (define (out-of-range x) (error "out of range" x))
> (define (not-int x) (error "expected an integer" x))
> (cond
>((fixnum? x)
> (if (<= -10 x 100)
> (* x 2)
> (out-of-range x)))
>((bignum? x)
> (if (<= -10 x 100)
> (* x 2)
> (out-of-range x)
> I'm sorry but I do not agree. Guile is not an implementation detail in
> this case. It means that the package is based on Guile. It's like xterm
> (a terminal for x window), gnome-terminal (a terminal based on the GNOME
> framework) and so on.
Hence many users who don't use Gnome won't use gnome
> Initially in Guile I planned to use GNU Lightning, in part because of
> its great platform support. However it turned out to not be the right
> thing, and reluctantly I ended up doing something that was more like a
> rewrite than a refactor.
[...]
> If someone would like to write an IA64 backend
>> I have actually signed the copyright assignment for the FSF already, but
>> only for gdb/binutils. I asked back then whether it would be possible to
>> sign the copyright assignment for all GNU projects but that was rejected.
> Yeah, that’s not possible.
Companies can do that for their employer
> +* Guile backtraces
Please add the Guile version here (ideally, the latest version known to
generate such backtraces).
> +(guile-file "^In \\(.+\\):\n" 1)
AFAICT this will mark those lines as errors (aka red) whereas I think
these should be marked as supplemental info (aka green).
Other t
> * progmodes/gud.el (guiler): New function. Starts the Guile REPL;
> add Guile debugger support for GUD.
Looks OK, tho please use the new `setq-local' when setting variables
buffer-locally.
Stefan
> This is a link to the PDF which is a Google drive doc:
>http://goo.gl/ioTpR7
No, it's not a link to a PDF document. It's a link to an
HTML+Javascript page that tries to render in your browser some PDF
document (to which I don't seem to have direct access).
Stefan
14 matches
Mail list logo
