> I came across a couple I've used that aren't documented.
> (...)
>
> scm_display
> scm_puts
These two are "documented" in the sense that they are used in the
manual, more precisely in chapter about smob for the print_image()
sample function.
So they are mean to be public I guess.
Hello all,
I have now produced two very different implementations of
`the-environment' and `local-eval' that support compilation.
Included below is a simple patch that I believe is ready for commit to
the stable-2.0 branch, and I very much hope it can be included in 2.0.4.
However, before I tell
Mark H Weaver writes:
> Hello all,
>
> I have now produced two very different implementations of
> `the-environment' and `local-eval' that support compilation.
>
> Included below is a simple patch that I believe is ready for commit to
> the stable-2.0 branch, and I very much hope it can be includ
> From: Bruce Korb
> My "(get ...)" function always returns a string.
> This result was assigned to "tmp-text" and the
> "(string-upcase ...)" is complaining that the input is
> read only. Well, it isn't, so the real complaint
> is being hidden by the "string is read-only" message.
>
> It work
Hi Mike,
Thank you for the explanation. However:
On 01/03/12 07:03, Mike Gran wrote:
It worked until I "upgraded" to openSuSE 12.1.
$ guile --version
guile (GNU Guile) 2.0.2
.
(set! tmp-text (get "act-text"))
(set! TMP-text (string-upcase tmp-text))
>>> ERROR: In pr
Hi!
Sorry for the terrible delay here.
On Sun 04 Sep 2011 07:33, Ian Price writes:
> Nala Ginrut writes:
>
>> hi guys!
>> I realized there're two problems in our shinning Guildhall.
>>
>> 1. When "http-download" calls "relative-uri", the first arg should be a
>> string, say "srfi", but ("srf
> From: Bruce Korb
> 2. it is completely, utterly wrong to mutilate the
> Guile library into such a contortion that it
> interprets this:
> (define y "hello")
> to be a request to create an immutable string anyway.
> It very, very plainly says, "make 'y' and fill it with
On Mon 22 Aug 2011 16:49, Thien-Thi Nguyen writes:
> I kind of dislike the "marked as a member of some group" meme, whether
> expressed as "guild" or "sigil". Traditionally, guilds were irascibly
> exclusive, subverting competition, introducing proprietary "extensions"
> and "trade marks", and (
() Andy Wingo
() Tue, 03 Jan 2012 11:35:07 -0500
I thought about this for a while, and considered other folks'
input, and in the end went back to the Guildhall name. "Sigil"
in modern days has too many connotations with crystals and
"magic".
I don't want to promote a "join and on
David Kastrup writes:
> How will either fare with:
>
> (let ((env
> (let ((x 1))
> (the-environment
> (local-eval '(set! x 4) env))
This example (or more complex ones based on the same idea) present no
difficulties for either patch.
scheme@(guile-user)> (use-modules (ice-9 local-e
Hi Mike!
Mike Gran skribis:
> It'll be fun to try to minimize it down to just
> the guile executable, libguile-*, and a scheme archive file. And it
> might help with distribution of prebuilt versions.
Are you saying that, say, Lilypond’s tarball would contain libguile.so
and the .go files? (I
Hi!
And happy new year! :-)
Mike Gran skribis:
> scm_display
A matter of adding it as a @deffnx below ‘display’ under “Scheme Write”.
> scm_puts
This and scm_putc should be documented, yes.
> scm_new_port_table_entry
Actually the whole port subsystem is undocumented. :-( So yes, would
b
Hi Bruce,
And happy new year!
Bruce Korb skribis:
> Thank you for the explanation. However:
>
> On 01/03/12 07:03, Mike Gran wrote:
>>> It worked until I "upgraded" to openSuSE 12.1.
>>>
$ guile --version
guile (GNU Guile) 2.0.2
.
>
(set! tmp-text (get "act-text
> From: Ludovic Courtès
>> scm_display
>
> A matter of adding it as a @deffnx below ‘display’ under “Scheme Write”.
>
>> scm_puts
>
> This and scm_putc should be documented, yes.
>
>> scm_new_port_table_entry
>
> Actually the whole port subsystem is undocumented. :-( So yes, would
> be
> From: Ludovic Courtès
> Hi Mike!
>
> Mike Gran skribis:
>
>> It'll be fun to try to minimize it down to just
>> the guile executable, libguile-*, and a scheme archive file. And it
>> might help with distribution of prebuilt versions.
>
> Are you saying that, say, Lilypond’s tarball woul
Eli Barzilay writes:
>> Syntax parameters[fn:1] are a mechanism for rebinding a macro
>> definition within the dynamic extent of a macro expansion. It
>> provides a convenient solution to one of the most common types of
>> unhygienic macro: those that introduce a special binding each time
>
> I'd
On 01/03/12 14:24, Ludovic Courtès wrote:
2. it is completely, utterly wrong to mutilate the
Guile library into such a contortion that it
interprets this:
(define y "hello")
to be a request to create an immutable string anyway.
It very, very plainly says, "make 'y' a
Hi Mike!
Mike Gran skribis:
>> From: Ludovic Courtès
> > Hi Mike!
>>
>> Mike Gran skribis:
>>
>>> It'll be fun to try to minimize it down to just
>>> the guile executable, libguile-*, and a scheme archive file. And it
>>> might help with distribution of prebuilt versions.
>>
>> Are you
Bruce,
Bruce Korb skribis:
> On 01/03/12 14:24, Ludovic Courtès wrote:
>>> 2. it is completely, utterly wrong to mutilate the
>>> Guile library into such a contortion that it
>>> interprets this:
>>> (define y "hello")
>>> to be a request to create an immutable string an
> From: Ludovic Courtès
> OK, but back to the example above, you wouldn’t want Lilypond’s tarball
> to contain these binaries, would you?
For Lilypond on Win32, where the culture is to download
compiled binaries, I'd want to be able to provide a download location
for a pre-compiled Win7 x86 lib
Here's an improved version of the patch. Most notably, I removed the
`#:to' parameter to `local-compile', since I realized it couldn't be
implemented properly anyway. I also updated the copyright notices to
2012 in all changed files, and made some other simplifications and
cleanups.
Best,
An hour and a half ago, Ian Price wrote:
> Eli Barzilay writes:
>
> >> the macro is used. Examples include an 'if' form that binds the
> >> result of the test to an 'it' binding, or class macros that
> >> introduce a special 'self' binding.
> >
> > The `abort' example is also popular, probably ev
On 01/03/12 15:33, Ludovic Courtès wrote:
Could you point me to the affected code? What would you think of using
string-copy as I suggested? The disadvantage is that you need to modify
your code, but hopefully that can be automated with a sed script or so;
the advantage is that it would work wi
Mike Gran writes:
> The libguile would be modified so that the .iso or .tar file would
> never be unpacked. Guile would look inside the .tar or .iso for the
> compiled .go files.
What is the advantage of including our own little read-only filesystem,
when every OS already provides this functio
> From: Mark H Weaver
> What is the advantage of including our own little read-only filesystem,
> when every OS already provides this functionality? Is it really
> significantly easier to install 3 files than to install 300?
>
> Admittedly, I can see how it might make a psychological difference
> In many systems it is desirable for constants (i.e. the values of literal
> expressions) to reside in read-only-memory. To express this, it is
> convenient to imagine that every object that denotes locations is
> associated with a flag telling whether that object is mutable or immutable.
Hello,
> Then it turned out that the string functions would now clear the
> high order bit on strings, so they are no longer byte arrays and
> there is no replacement but to roll my own. I stopped supporting
> byte arrays. A noticable nuisance.
This is just a side note to the main discussion, b
Mike Gran writes:
>> From: Mark H Weaver
>
>> What is the advantage of including our own little read-only filesystem,
>> when every OS already provides this functionality? Is it really
>> significantly easier to install 3 files than to install 300?
>>
>> Admittedly, I can see how it might make
28 matches
Mail list logo
