lisp.org/display/120245
From 61900d7e93780dd9d7d6db02fe3ad07a72a8a45b Mon Sep 17 00:00:00 2001
From: Clinton Ebadi
Date: Sat, 5 Mar 2011 23:44:23 -0500
Subject: [PATCH] 2011-03-05 Clinton Ebadi
* libguile/regex-posix.c (scm_regexp_exec): Only fixup byte to
character offset when the str
Daniel Kraft writes:
> Hi,
>
> I think I got the test-suite as well as a basic macro implementation
> (the compiler framework is really cool, that was fairly easy to do);
> recursive macros do not yet work, but otherwise it looks fine.
>
> However, I want to tackle quasi-quotes (besides others) n
Daniel Kraft writes:
> Hi all,
>
> 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.
>
> Below is a proposal for a GSoC project I submitted to GNU as mentoring
> organization; Karl B
Linas Vepstas writes:
> An alternative idea is to try to apply some principles from
> functional programming, e.g. "copy on write" (COW): when
> the obarray needs to be updated, make a copy of it. Any
> readers in other threads continue to safely use the
> original version. When the new obarray i
l...@gnu.org (Ludovic Courtès) writes:
> Hello,
>
> Andy Wingo writes:
>
>> The compiler is almost to the point that it can replace the interpreter,
>> semantically. What is needed is to read and compile toplevel definitions
>> one at a time, so we can e.g. change the reader, or the other dynamic
Mike Gran writes:
> Hi,
>
> Let's say that one possible goal is to add wide strings
> * using Gnulib functions
> * with minimal changes to the public Guile API
> * where chars become 4-byte codepoints and strings are internally
> either UTF-32 or ISO-8859-1
>
> Since I need this functionalit
Neil Jerram writes:
> l...@gnu.org (Ludovic Courtès) writes:
>
>>> +(define *value-help-handlers* '())
>>
>> The convention within Guile is rather `%'-prefixed names for globals, as
>> in `%load-path'.
>
> I'm not sure about that. I interpret `%' as something to do with the
> "system" (e.g. when
Neil Jerram writes:
>> The problem is,
>> of course, that if you scm_init_guile in some .so,
>> you will accidentally place the entire system into guile
>> mode, and not just the .so, as intended.
>
> Or, to put that another way, the "guile mode"-ness persists on the
> thread that called your lib
"Pach Roman (DGS-EC/ESG3)" <[EMAIL PROTECTED]> writes:
>>> test 2:
>>> ---
>>> (define-macro (my-macro-2 par1 par2 par3)
>>> (string-concatenate (list par1 par2 par3)))
A macro defined with define-macro is merely a function that is run at
macroexpansion time and is expected to return a new
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
> Neil Jerram escreveu:
>> 2008/9/2 Han-Wen Nienhuys <[EMAIL PROTECTED]>:
>>> If you are doing memq? for something you already know to
>>> somewhere in front of the list [...]
>>
>> Why would you do that? In two senses:
>>
>> 1. I know memq gives you
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
> Ludovic Courtès escreveu:
Guile's string API is aiming not to be 8-bit-assuming, and I would
guess from the code above that the C++ string class is 8-bit-assuming.
>>> Sorry, I guess I don't understand. What _is_the assumption for
>>> repres
Clinton Ebadi <[EMAIL PROTECTED]> writes:
>> Is this okay, and in case not, is there a better way to convert a
>> char* into a guile string?
>
> SCM_API SCM scm_from_locale_string (const char *str);
> SCM_API SCM scm_from_locale_stringn (const char *str,
"Kjetil S. Matheussen" <[EMAIL PROTECTED]> writes:
> Bill Schottstaedt:
>>
>>> `scm_i_string_chars ()' is used by Mailutils, Lilypond, AutoGen, SND
>>
>> I'm not knowingly using any scm_i_* entities in Snd. I removed the
>> scm_i_procedure_arity use, and I think the SCM_STRING_CHARS macro
>> is o
Neil Jerram <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] (Ludovic Courtès) writes:
>
>> Hi Andreas,
>>
>> Andreas Rottmann <[EMAIL PROTECTED]> writes:
>>
>>> You should probably also have a look at the Scheme-Level FFI of PLT
>>> Scheme[1], and my reimplementation for Scheme 48[2].
>>
>> Thanks
Oops, forgot .diff
Index: gds-scheme.el
===
RCS file: /cvsroot/guile/guile/guile-core/emacs/gds-scheme.el,v
retrieving revision 1.4
diff -u -r1.4 gds-scheme.el
--- gds-scheme.el 17 Jan 2007 13:38:17 - 1.4
+++ gds-scheme.el 31 Jan
exist.
2007-01-31 Clinton Ebadi <[EMAIL PROTECTED]>
* gds-scheme.el (gds-display-results): Use save-selected-window
instead of switching to other-window in order to return to the
proper window in frames with more than two windows
gds-scheme.el
Description: appli
On Wed, 2006-05-31 at 10:49 +0200, Ludovic Courtès wrote:
> You can get it from my Arch archive:
>
> $ tla register-archive http://www.laas.fr/~lcourtes/software/arch-2005
> $ tla get -A [EMAIL PROTECTED] guile-core--boehm-gc--1.9 \
> guile-core--bgc
>
> A tarball and a diff against c
On Sat, 2006-05-06 at 00:02 +0200, Martin Kuehl wrote:
> Damn, macros again :-)
> I'll definitely take a look at the revival, but I really doubt I'm the
> one to take on first-class macros just yet. I seem to have a hard
> time reasoning about them instead of CL macros (or maybe I just
> confuse t
When I was running through the evaluator code, I noticed the comment on
SCM_UNBOUND (only used by GOOPS), and that it should be replaced by
SCM_UNSPECIFIED.
Defining SCM_GOOPS_UNBOUND to SCM_UNDEFINED seemed to work:
guile> (version)
"1.9.0"
guile> (use-modules (oop goops))
guile> (define-class
19 matches
Mail list logo
