Re: GPT-4 knows Guile! :)

> > On Sat, Mar 18, 2023 at 11:01 AM wrote: > >> On Sat, Mar 18, 2023 at 10:03:15AM +0100, Mikael Djurfeldt wrote: >> >> [...] >> >> > > I know very little apart from knowing what deep learning is and having >> > > skimmed the "Atte

Re: GPT-4 knows Guile! :)

Also: do you have a mechanism to avoid controversy As an AI language model, I am designed to prioritize providing accurate and helpful information while aiming to be neutral and unbiased. My developers at OpenAI have implemented guidelines to help me avoid generating content that is offensive,

Re: GPT-4 knows Guile! :)

On Sat, Mar 18, 2023 at 9:58 AM Mikael Djurfeldt wrote: > On Sat, Mar 18, 2023 at 9:46 AM wrote: > >> On Sat, Mar 18, 2023 at 09:41:37AM +0100, Mikael Djurfeldt wrote: >> > On Sat, Mar 18, 2023 at 9:36 AM wrote: >> >> [...] >> >> > > Perh

Re: GPT-4 knows Guile! :)

On Sat, Mar 18, 2023 at 9:46 AM wrote: > On Sat, Mar 18, 2023 at 09:41:37AM +0100, Mikael Djurfeldt wrote: > > On Sat, Mar 18, 2023 at 9:36 AM wrote: > > [...] > > > > Perhaps you didn't know, but you are training the model :-) > > > > > > > Unfo

Re: GPT-4 knows Guile! :)

On Sat, Mar 18, 2023 at 9:36 AM wrote: > On Sat, Mar 18, 2023 at 09:22:43AM +0100, Mikael Djurfeldt wrote: > > BTW, in the bouncing ball example, I find it amazing that I could get an > > improvement of the code by complaining: > > > > But all those SDL_ calls look

Re: GPT-4 knows Guile! :)

On Sat, Mar 18, 2023 at 9:14 AM wrote: > This is what I was hinting at with that pastiche of Hanlon's Razor > and Clarke's Third Law. If you're doing statistical "AI", no harm > is provably intended. But the dice might be loaded ;-) > Yes, this is an important point. And it is sometimes

Re: GPT-4 knows Guile! :)

BTW, in the bouncing ball example, I find it amazing that I could get an improvement of the code by complaining: But all those SDL_ calls look like C bindings. Please use guile-sdl2 bindings. (It was also quite entertaining that I had to ask it to write the code "according to the guile-sdl2

Re: GPT-4 knows Guile! :)

On Sat, Mar 18, 2023 at 8:55 AM Mikael Djurfeldt wrote: > >1. Install Guile: > >> > >> > csharp >> ^^ >> > >> > sudo apt-get install guile-2.2 >> >> [...] >> >> Did it literally write "csharp"? With s

Re: GPT-4 knows Guile! :)

>1. Install Guile: > > > > csharp > ^^ > > > > sudo apt-get install guile-2.2 > > [...] > > Did it literally write "csharp"? With some fantasy, I guess it > is trying to evoke a root shell, but with some malice, I'd say > Microsoft is sleazily touting some product of theirs. > No, in

Re: GPT-4 knows Guile! :)

Can you write a Guile Scheme program which displays a bouncing ball? As an AI language model, I cannot create a full graphical program directly within this text-based environment. However, I can provide you with an example of a simple bouncing ball simulation using the Guile Scheme programming

GPT-4 knows Guile! :)

Mikael: Let's write a scheme program which randomly makes names by combining two words from a list. To write a Scheme program that generates random names by combining two words from a list, you can use the following code: scheme (import (scheme random)) ; Import random number generation

Re: [PATCH] Fix minor typos

Thanks Colin and Aleix, This has been committed (856c3f96). Best regards, Mikael On Fri, Dec 2, 2022 at 6:44 PM Aleix Conchillo Flaqué wrote: > On Thu, Dec 1, 2022 at 10:10 PM Colin Woodbury wrote: > >> `make html` should do it. The output is in doc/ref/guile.html/index.html >> >> Yup, that

Re: Feature request: Ability to document variables like defvar in elisp

(define a 5) (set-object-property! (module-variable (current-module) 'a) 'documentation "The variable a contains a number.") ? On Wed, Nov 2, 2022 at 9:29 AM Jean Abou Samra wrote: > Le 02/11/2022 à 02:08, Jacob Hrbek a écrit : > > The ability to document variables is critical for many

Re: map-par slower than map

A piece of background on par-map: When I introduced par-map et al the only ambition was to have simple language constructs to invoke parallelism. The use case I had in mind was course grained parallelism where each piece of work is somewhat substantial. Back then, a thread was launched for each

Re: map-par slower than map

Also, I would believe that any crashes in this context are neither due to the futures implementation nor par-map et al. I would think that crashes are due to the Guile basic thread support itself. On Tue, Oct 25, 2022 at 11:07 AM Mikael Djurfeldt wrote: > A piece of background on par-

Re: Hatables are slow

I agree. Also, if there is no strong reason to deviate from RnRS, that would be a good choice. (But, I'm also no maintainer.) On Wed, Feb 23, 2022 at 8:42 AM Linus Björnstam < linus.bjorns...@veryfast.biz> wrote: > Hej! > > I would also propose a hash table based on a more sane interface. The >

Re: Hatables are slow

(Note that the resizing means *rehashing* of all elements.) On Mon, Feb 21, 2022 at 11:17 PM Mikael Djurfeldt wrote: > The hash table in Guile is rather standard (at least according to what was > standard in the old ages :). (I *have* some vague memory that I might have > implemented

Re: Hatables are slow

The hash table in Guile is rather standard (at least according to what was standard in the old ages :). (I *have* some vague memory that I might have implemented a simpler/faster table at some point, but that is not in the code base now.) The structure is a vector of alists. It's of course

Re: Pausable continuations

Hi, I'm trying to understand this. The example of a generator which you give below counts upwards, but I don't see how the value of n is passed out of the generator. Could you give another example of a generator which does pass out the values, along with a usage case which prints out the values

Re: (inf) min max

The proper way to handle this would, as you suggest, be to distinguish different kinds on infinities. Then, perhaps, countable infinity could be regarded as scheme:ish exact while infinities of higher cardinality would not (since scheme's handling of that kind of numbers is an approximation and,

Re: Python-on-guile

gt;> (let/ec x (f x >>> >>> Actually lead to similar speeds as python3. >>> >>> >>> >>> On Sat, Apr 24, 2021 at 1:26 PM Stefan Israelsson Tampe < >>> stefan.ita...@gmail.com> wrote: >>> >>>> Pro tip, w

Re: Python-on-guile

(I should perhaps add that my script doesn't benchmark the object system but rather loops, conditionals and integer arithmetic.) Den fre 23 apr. 2021 17:00Mikael Djurfeldt skrev: > Hi, > > Yesterday, Andy committed new code to the compiler, some of which > concerned skipping some arity

Python-on-guile

Hi, Yesterday, Andy committed new code to the compiler, some of which concerned skipping some arity checking. Also, Stefan meanwhile committed something called "reworked object system" to his python-on-guile. Sorry for coming with unspecific information (don't have time to track down the

Re: Python on guile v1.2.3.7

Hi Stefan, Could it be that you have not committed the file: language/python/module/re/flag-parser.scm ? Best regards, Mikael On Sun, Apr 11, 2021 at 11:23 AM Stefan Israelsson Tampe < stefan.ita...@gmail.com> wrote: > Hi, > > I released a new tag of my python code that basically is a

Re: garbage collection slowdown

Den ons 5 feb. 2020 23:32Han-Wen Nienhuys skrev: > > > On Wed, Feb 5, 2020 at 5:23 PM Ludovic Courtès wrote: > >> Weird. It would be interesting to see where the slowdown comes from. >> Overall, my recollection of the 1.8 to 2.0 transition (where we >> introduced libgc) is that GC was a bit

Re: GNU Guile 2.9.9 Released [beta]

mpe < stefan.ita...@gmail.com> wrote: > > > -- Forwarded message - > From: Stefan Israelsson Tampe > Date: Tue, Jan 14, 2020 at 5:23 PM > Subject: Re: GNU Guile 2.9.9 Released [beta] > To: Mikael Djurfeldt > > > This is how it always have been

Re: GNU Guile 2.9.9 Released [beta]

Dear Andy, I probably don't have a clue about what you are talking about (or at least hope so), but this---the "eq change"---sounds scary to me. One of the *strengths* of Scheme is that procedures are first class citizens. As wonderfully show-cased in e.g. SICP this can be used to obtain

Re: landed r7rs support

Wonderful! Then I guess the texts in sections 9.1.5 and 9.4.7 in the manual should be updated? I would have submitted a patch if I knew better how to reformulate. Best regards, Mikael On Sun, Nov 17, 2019 at 3:45 PM Andy Wingo wrote: > Hey all :) > > Just a little heads-up that I just landed

Re: guile 3 update, halloween edition

Saying this without having looked at your code and also without currently promising to do any work: How does the record subtyping relate to GOOPS? I do realize that there are issues related to keeping bootstrapping lean, but shouldn't record types and classes share mechanisms? Best regards,

Re: Guile and Mes [WAS: conflicts in the gnu project now affect guile]

On Sat, Oct 19, 2019 at 9:52 AM Jan Nieuwenhuizen wrote: > Mark H Weaver writes: > Our next big target for Mes should be > to remove define-macro support from eval_apply and load Guile's > psyntax-pp.scm. > A word of caution here: Running psyntax-pp.scm without optimization is dog slow. Best

Re: Stepping back up as a co-maintainer

I think we should trust what Mark says and not second guess him. Helping or being friend with someone is not among the worst crimes on my list. Den tors 17 okt. 2019 11:28zx spectrumgomas skrev: > I'm a simple Guile user and I hope I'm wrong, but I think Mark H weaver are > saying half-thruth

Re: conflicts in the gnu project now affect guile

Hi Andy, Ludovic and everyone else, As a previous co-maintainer of Guile, it saddens me that you/we have run into these kind of difficulties. It's especially sad since, as also David wrote, Guile has always been a project with a friendly atmosphere. What I wish for is that everyone involved in

Re: Maintainership changes: many thanks to Mark!

Mark, Ludovic and Andy, Warm regards and many, many thanks for your great work! Mikael Den ons 11 sep. 2019 09:57Andy Wingo skrev: > Hi all, > > After many years working on Guile and more than 5 years in a > maintainer role, Mark Weaver has decided to step down. Taking over > from him and

(ice-9 peg string-peg)

Hi, The functions in (ice-9 peg string-peg) are not re-exported by (ice-9 peg) which can be confusing to the user, since the manual only mentions (ice-9 peg). Can I, for simplicity, make (ice-9 peg) re-export (ice-9 peg string-peg) functions?

FOSDEM 2019

It was a great experience and joy for me to meet some of you at FOSDEM 2019. Thank you all! Now a piece of advice. Everyone who works with Guile knows that it's crap and look with envy at projects like Chez and Racket, right? Jim Blandy thinks that GNU should use Python as its scripting

Re: Results of tests of guile-2.9

It would be nice to have guile-1.8 in that list since some users stayed at that version due to 2.0 being slower. Maybe, in time, we can get everyone back to the most recent release. :-)) Den tis 13 nov. 2018 00:48 skrev Mikael Djurfeldt : > Thanks, Arne! > > Den mån 12 nov. 2018 01

Re: Results of tests of guile-2.9

Thanks, Arne! Den mån 12 nov. 2018 01:04 skrev Arne Babenhauserheide : > > Mikael Djurfeldt writes: > > > That sounds great! Can you say something about how much quicker 2.9.1 is > > compared to 2.2? > > You can find that by looking at the benchmarks by ecraven: &g

Re: Results of tests of guile-2.9

That sounds great! Can you say something about how much quicker 2.9.1 is compared to 2.2? Den sön 11 nov. 2018 21:53 skrev Stefan Israelsson Tampe < stefan.ita...@gmail.com>: > Hi, > > I've taken 2.9 on a ride with my active code bases, guile-log, > guile-syntax-parse and python-on -guile. > >

Re: A different stack discipline

Den lör 3 nov. 2018 19:16 skrev Mikael Djurfeldt : > On Sat, Nov 3, 2018 at 4:30 PM Hugo Hörnquist wrote: > >> The section, as far as I can see, just describes a machine >> which pushes continuation instead of the PC counter to the >> stack. >> >> Als

Re: Proposal for a new (ice-9 history)

I've thought some more about this. What this is about is a need to refer to previous values in value history in a relative way rather than referring specifically to some historic value. First a simple (and perhaps not so useful) example, where we use Heron's method to compute the square root of

Re: Proposal for a new (ice-9 history)

On Tue, Oct 30, 2018 at 2:59 PM Mikael Djurfeldt wrote: > > Is it a problem that this would drag in many modules at start-up? > I checked. It turns out that all modules used by (ice-9 vlist) are loaded anyway. (Otherwise, (language cps intmap) is an option too. :-)

Re: Proposal for a new (ice-9 history)

On Tue, Oct 30, 2018 at 7:21 AM Mark H Weaver wrote: > Hi Mikael, > > Mikael Djurfeldt writes: > > > On Tue, Oct 30, 2018 at 1:26 AM Mark H Weaver wrote: > > > > Mikael Djurfeldt writes: > > > > > The interface of (value-history) would ins

Re: REPL and load deifferences (was Re: Proposal for a new (ice-9 history))

And, the attachments... On Tue, Oct 30, 2018 at 11:21 AM Mikael Djurfeldt wrote: > On Tue, Oct 30, 2018 at 1:55 AM Mikael Djurfeldt > wrote: > >> On Tue, Oct 30, 2018 at 12:55 AM Mark H Weaver wrote: >> >>> More precisely, it is a literal >>> ident

REPL and load deifferences (was Re: Proposal for a new (ice-9 history))

On Tue, Oct 30, 2018 at 1:55 AM Mikael Djurfeldt wrote: > On Tue, Oct 30, 2018 at 12:55 AM Mark H Weaver wrote: > >> More precisely, it is a literal >> identifier recognized by 'match' and related macros, in the same sense >> that 'else' and '=>' are lit

Re: Proposal for a new (ice-9 history)

On Tue, Oct 30, 2018 at 1:26 AM Mark H Weaver wrote: > Mikael Djurfeldt writes: > > > The interface of (value-history) would instead have a lazy-binder > > which provides a syntax transformer for every $... actually being > > used. The $... identifier would expand into a

Re: Proposal for a new (ice-9 history)

On Tue, Oct 30, 2018 at 12:55 AM Mark H Weaver wrote: > However, there's a complication with using '$' in this way. '$' is > already widely used as part of the syntax for (ice-9 match), to specify > patterns that match record objects. Yes, I actually looked at this, but thought that $ would

Re: Officially require GNU Make to build Guile? (was Re: Bootstrap optimization)

On Sun, Oct 28, 2018 at 11:34 PM Mark H Weaver wrote: > I'm still inclined to consider it a bug, but maybe we can have the best > of both worlds here. I see that Automake has conditionals: > > https://www.gnu.org/software/automake/manual/automake.html#Conditionals > > How hard would it be to

Re: Bootstrap optimization

2002) or later, but that shouldn't be a problem, right? Best regards, Mikael From 332471874aa227e8b25b747f560ab9185af4f2fb Mon Sep 17 00:00:00 2001 From: Mikael Djurfeldt Date: Thu, 25 Oct 2018 13:53:47 +0200 Subject: [PATCH] Bootstrap optimization * bootstrap/Makefile.am: Build both eval.go

Re: Bootstrap optimization

Den sön 28 okt. 2018 02:35Mark H Weaver skrev: > The downside of this approach to serialization is that when we add file > X.scm to the list of objects to build serially, we force a full rebuild > whenever X.scm is modified. At present, eval.scm is the only file that > forces a full rebuild.

Add dependency on texinfo in README

Does this make sense (see attached patch)? Forgetting to install the texinfo packages has bitten myself several times. From 732fe1af508aeb65588981839dfc01172ec79f0e Mon Sep 17 00:00:00 2001 From: Mikael Djurfeldt Date: Wed, 24 Oct 2018 20:56:16 +0200 Subject: [PATCH] Add texinfo dependency

Re: GNU Guile 2.9.1 Released [beta]

version 2 of the benchmarks. (BTW, on my machine the previous version is better at provoking a segfault.) ramanujan.scm -- Compute the N:th Ramanujan number Copyright (C) 2018 Mikael Djurfeldt This program is free software; you can redistribute it and/or modify

Re: GNU Guile 2.9.1 Released [beta]

, Mikael On Thu, Oct 11, 2018 at 12:49 AM Mikael Djurfeldt wrote: > Congratulations to fantastic work! > > I wonder if your evaluator speed estimates aren't too humble? > > With this email, I attach scheme and python versions of a (maybe > buggy---just wrote it) algorithm for finding

Re: GNU Guile 2.9.1 Released [beta]

part of the machinery for class redefinition > and is no longer needed. > > ** VM hook manipulation simplified > > The low-level mechanism to instrument a running virtual machine for > debugging and tracing has been simplified. See "VM Hooks" in the > manual, for more

Re: guile 3 update: instruction explosion for pairs, vectors

On Tue, Jan 16, 2018 at 4:55 PM, Andy Wingo wrote: > Thinking more globally, there are some more issues -- one is that > ideally we need call-site specialization. A GF could be highly > polymorphic globally but monomorphic for any given call site. We need > away to specialize.

Re: guile 3 update: instruction explosion for pairs, vectors

Hi, Hi think this is a marvelous development and, for what it's worth, in the right direction. Many, many thanks! Maybe this is all completely obvious to you, but I want to remind, again, about the plans and ideas I had for GOOPS before I had to leave it at its rather prototypical and unfinished

Re: Hook vs. list of procedures

Can I just add this: First, as Andy already hinted, it's not how a data type is implemented but the operations in its API which defines it. A list does not map directly to a hook. A hook can be implemented as a list, but that is not important. An example of a hook is before-print-hook which is

Re: Native code generation and gcc

limiting the size of the cache such that the counters compete for available space. (There are further issues to consider such as adaptability through forgetting, but I won't make this discussion even more complicated.) Best regards, Mikael On Mon, Dec 5, 2016 at 5:18 PM, Lluís Vilanova <vila

Native code generation and gcc

[I apologize beforehand for being completely out of context.] Are there fundamental reasons for not re-using the gcc backends for native code generation? I'm thinking of the (im?)possibility to convert the cps to some of the intermediate languages of gcc. If it wouldn't cause bad constraints the

Re: Guile & Emacs chat at emacs hackathon/bug-crush SF

This is wonderful news! :-) I've actually tried out guile-emacs recently. What would be wonderful to have is some kind of simple "map" over what has been done so far (e.g. the large-scale structure of the code and what the relationship between the elisp and guile interpreter currently is). Maybe

Re: [PATCH] Append effective version to GUILE_LOAD[_COMPILED]_PATH

In python, the version number is higher up in the directory hierarchy, which, hypothetically, allows newer versions to have "inventions" in the more detailed directory structure: /usr/lib/python2.6 /usr/lib/python2.7 etc Just a thought. On Fri, Mar 4, 2016 at 2:13 PM, Jan Nieuwenhuizen

Guile compilation time

Is there an easy way to replace the bootstrap interpreter with an already built Guile in order to speed up the build process?

Re: Asynchronous event loop brainstorm at FSF 30

On Wed, Nov 18, 2015 at 3:16 PM, Christopher Allan Webber <cweb...@dustycloud.org> wrote: > Mikael Djurfeldt writes: > >> Den 4 okt 2015 02:30 skrev "Christopher Allan Webber" < >> cweb...@dustycloud.org>: >>> - This would be like asyncio or node.js, as

Re: Asynchronous event loop brainstorm at FSF 30

Den 4 okt 2015 02:30 skrev "Christopher Allan Webber" < cweb...@dustycloud.org>: > - This would be like asyncio or node.js, asynchronous but *not* OS >thread based (it's too much work to make much of Guile fit around >that for now) Why is this (too much work for threads)?

Re: [PATCH] Avoid GOOPS in (system foreign-object)?

On Fri, May 22, 2015 at 10:42 AM, Ludovic Courtès l...@gnu.org wrote: Just wanted to say that I think that we (or at least I) at some point in time had the goal to replace structs with pure GOOPS data structures. In the context of FFI, this would allow you to be more flexible than what

Re: [PATCH] Avoid GOOPS in (system foreign-object)?

Hi Ludovic, Sadly, I nowadays only have time to look at guile-devel briefly now and then. I did this now and happened to see this. Just wanted to say that I think that we (or at least I) at some point in time had the goal to replace structs with pure GOOPS data structures. In the context of

Re: Precedence for reader extensions

Thanks, Mark. This all sounds very sensible to me, and I will continue working on the scmutils port while waiting for your patch. On Fri, Feb 22, 2013 at 3:52 AM, Mark H Weaver m...@netris.org wrote: Mikael Djurfeldt mik...@djurfeldt.com writes: The API you suggest would compose much easier

Re: Precedence for reader extensions

On Tue, Feb 19, 2013 at 12:33 AM, Mark H Weaver m...@netris.org wrote: Mikael Djurfeldt mik...@djurfeldt.com writes: I propose to simplify this to only two levels: 1. %read-hash-procedures 2. predefined syntax It turns out that the change I propose above was already implemented in read.c

Re: Precedence for reader extensions

On Tue, Feb 19, 2013 at 4:41 PM, Mark H Weaver m...@netris.org wrote: Mikael Djurfeldt mik...@djurfeldt.com writes: On Tue, Feb 19, 2013 at 12:33 AM, Mark H Weaver m...@netris.org wrote: Mikael Djurfeldt mik...@djurfeldt.com writes: I propose to simplify this to only two levels: 1. %read

Re: Precedence for reader extensions

On Tue, Feb 19, 2013 at 5:42 PM, Mikael Djurfeldt mik...@djurfeldt.com wrote: * The suggested change does compose What I meant here is that it does compose with the built-in syntax. Of course, the %read-hash-procedures API by itself doesn't automatically compose if multiple user-defined modules

Re: Precedence for reader extensions

On Tue, Feb 19, 2013 at 5:42 PM, Mikael Djurfeldt mik...@djurfeldt.com wrote: * The suggested change *does* make things conceptually simpler and more flexible (= you can always override hash syntax if you want; compared to the current: you can override #| but not other hash syntax) Just

Precedence for reader extensions

I'm working on an mit-scheme compatibility module (compat mit-scheme) enabling Guile to read a (so far) subset of mit-scheme code. Now I have the problem that mit-scheme has the two constants #!optional and #!rest (mit-scheme extensions to the scheme standard). I thought that I could support

Re: Precedence for reader extensions

On Mon, Feb 18, 2013 at 10:05 PM, Mikael Djurfeldt mik...@djurfeldt.com wrote: guilehall guildhall (I write too fast)

Re: Precedence for reader extensions

On Mon, Feb 18, 2013 at 10:05 PM, Mikael Djurfeldt mik...@djurfeldt.com wrote: If anyone is afraid about the effect this would have on reader performance, it is possible to compile %read-hash-procedures to a table of flags indicating exceptions. But, given the current interface to reader

Re: Precedence for reader extensions

(Sorry for thinking publicly.) The reason why I don't simply use guile-reader but start bugging you about it is that it feels silly that Guile, which was originally supposed to be able to support different languages, can't even support the read syntax of a sibling scheme interpreter. It is

Re: syntax closures

Just saw this. Right, syntactic closures is the name of a macro system by Alan Bawden and Jonathan Rees: http://en.wikipedia.org/wiki/Syntactic_closures http://www.gnu.org/software/mit-scheme/documentation/mit-scheme-ref/Syntactic-Closures.html#Syntactic-Closures So, it would be good to choose

Re: Scmutils in guile-2.0

Daniel Gildea reported problems for guile-2.0 guile-scmutils. Those are fixed in the attached diff. Best regards, Mikael D. guile-scmutils-v0.8-2.0-2.diff Description: Binary data

Re: Scmutils in guile-2.0

On Fri, Feb 8, 2013 at 10:54 AM, Ludovic Courtès l...@gnu.org wrote: Mikael Djurfeldt mik...@djurfeldt.com skribis: On Thu, Feb 7, 2013 at 11:00 PM, Ludovic Courtès l...@gnu.org wrote: +(cond-expand (guile-2 + (define-syntax define-integrable + (syntax-rules

Scmutils in guile-2.0

As an exercise before porting the up-to-date version of scmutils, I eventually decided to bring Daniel Gildea's Guile port up-to-date. You'll find the archive guile-scmutils-v0.8.tgz here: http://www.cs.rochester.edu/~gildea/guile-scmutils/ You should be able to apply the attached patch and

Re: Scmutils in guile-2.0

On Thu, Feb 7, 2013 at 11:00 PM, Ludovic Courtès l...@gnu.org wrote: +(cond-expand (guile-2 + (define-syntax define-integrable + (syntax-rules () + ((_ form body ...) (define form body ...) You can actually use ‘define-inlinable’ here (info (guile)

Re: Fixing the slib mess

22 Oct 2012 01:11, Mikael Djurfeldt mik...@djurfeldt.com writes: When trying to use guile 2 for logic programming I discovered that the slib interface is again broken (and has been for quite some time). I am very sorry that I did not see this thread before hacking on this recently. Somehow

Re: Fixing the slib mess

On Mon, Oct 22, 2012 at 11:51 PM, Mark H Weaver m...@netris.org wrote: It looks to me like your current implementation of 'syntax-toplevel?' is actually testing for a top-level _syntactic_ environment, but what you ought to be testing for here is slightly different. You are absolutely right.

Re: Fixing the slib mess

On Tue, Oct 23, 2012 at 8:01 PM, Mark H Weaver m...@netris.org wrote: Anyway, here's another idea: after requiring a new slib package, iterate over the entire list of top-level bindings in the slib module and export everything. What do you think? I think it sounds like the best idea so far.

Re: Fixing the slib mess

On Mon, Oct 22, 2012 at 8:31 PM, Stefan Israelsson Tampe stefan.ita...@gmail.com wrote: Comments? Can I add syntax-toplevel? to psyntax.scm and (system syntax)? [...] I can answer with some kind of suggestion here. in (system syntax) there is syntax-local-binding which you can use for

Re: Fixing the slib mess

On Mon, Oct 22, 2012 at 1:11 AM, Mikael Djurfeldt mik...@djurfeldt.com wrote: Comments? Can I add syntax-toplevel? to psyntax.scm and (system syntax)? Do you think it is reasonable to submit something along the line of guile.init.diff to slib guile.init? If I get an OK, then I would

Fixing the slib mess

interface to the new Guile uniform arrays, so there's a lot of slib functionality which won't yet work. Comments? Can I add syntax-toplevel? to psyntax.scm and (system syntax)? Do you think it is reasonable to submit something along the line of guile.init.diff to slib guile.init? Best regards, Mikael

Benchmarks

Dear Guilers, I just pulled the latest version via git and am amazed about how much you have achieved during the last years. Then, today, I stumbled on this: http://www.cs.utah.edu/~mflatt/benchmarks-20100126/log3/Benchmarks.html Probably Guile now compares better to the other

Re: notes on the goops dispatch implementation

2008/10/19 Andy Wingo [EMAIL PROTECTED]: I have been going through GOOPS more carefully recently, preparing to make GOOPS and code that uses GOOPS compilable, preserving all of the intended optimizations. It turns out the dispatch mechanism is rather interesting. I write about it here:

Re: Goops Valgrind

2008/9/11 Neil Jerram [EMAIL PROTECTED]: Also, is Mikael right with his error #1? I'm thinking not, because I believe that instances are structs too, so surely it's OK to call SCM_STRUCT_DATA (x)[...] on them? It is good that you are sceptical about what I say because it was a long time ago

Re: let's bytecode it!

2008/4/25 Ludovic Courtès [EMAIL PROTECTED]: Guile-VM is written as an independent project currently, so I don't think it would fit well into core Guile, and I'm actually not sure it'd be a good idea to put it there, at least for now. [Jumping in again although I shouldn't since I don't

Re: fixes to goops + light structs + 'u' slots

2008/4/19, Andy Wingo [EMAIL PROTECTED]: I wash my hands. :-) When I left, structs where two words. commit 08c880a36746289330f3722522960ea21fe4ddc8 Author: Mikael Djurfeldt [EMAIL PROTECTED] It is natural for our memory to fade over this much time ;-) But if at any point something

Re: fixes to goops + light structs + 'u' slots

2008/4/16, Andy Wingo [EMAIL PROTECTED]: On Sun 13 Apr 2008 21:09, Mikael Djurfeldt [EMAIL PROTECTED] writes: I then ran accessor ref tests on objects that necessarily had their slots bound, and thus would go through @assert-bound-ref: (3) If the determination can be made that the slot

Re: fixes to goops + light structs + 'u' slots

2008/4/16, Mikael Djurfeldt [EMAIL PROTECTED]: 2008/4/16, Andy Wingo [EMAIL PROTECTED]: On Sun 13 Apr 2008 21:09, Mikael Djurfeldt [EMAIL PROTECTED] writes: I then ran accessor ref tests on objects that necessarily had their slots bound, and thus would go through @assert-bound-ref

Re: fixes to goops + light structs + 'u' slots

2008/4/14, Andy Wingo [EMAIL PROTECTED]: I have shied away from GOOPS internals in the past, but every time I have a brush with them I learn something interesting. You're very kind. It's in large parts not easily readable code. What is your perspective regarding foreign-slot? I wrote a bit

Re: fixes to goops + light structs + 'u' slots

2008/4/14, Andy Wingo [EMAIL PROTECTED]: Is this designed to work? It seems that all is still not right, @slot-ref (only used in accessors, not in slot-ref) accesses the slot as a SCM Right, the special form is @slot-ref, not @assert-bound-ref as I stated previously.

Re: stack overflow

2008/2/17, Han-Wen Nienhuys [EMAIL PROTECTED]: Isn't it be possible to catch SIGSEGV, and check whether it was caused by overflow? Couldn't that leave the interpreter in a strange state so that one would need to quit and restart? The current scheme allows the interpreter to continue to run

Re: stack overflow

2008/2/14, Ludovic Courtès [EMAIL PROTECTED]: Speaking as a user, I would prefer a solution where the evaluator measures stack size the same way as currently (i.e. without the need to do extra work at every return). It is possible to estimate the average sizes of evaluator stack

Re: the future of Guile

2007/12/4, Marco Maggi [EMAIL PROTECTED]: I think that it is time for a chat on the future of Guile. Some pieces of input to the discussion: * There is (or should be) a module called workbook in the repository. It contains policy documents setting out the direction for Guile development. It

Re: SLIB

2007/8/11, Ludovic Courtès [EMAIL PROTECTED]: I'd like to fix the SLIB issue in 1.8.3. SLIB 3a4 works perfectly well with 1.8. The thing is that `(ice-9 slib)' is of no use. It's of no use since no-one has added the functions which Aubrey have added to guile.init when changing slib:s

Re: Heads up: Releasing 1.8.2

2007/6/25, Greg Troxel [EMAIL PROTECTED]: guile guile (use-modules (ice-9 slib)) WARNING: (guile-user): imported module (ice-9 slib) overrides core binding `provide' WARNING: (guile-user): imported module (ice-9 slib) overrides core binding `provided?' guile (version) 1.8.1 guile The problem

Re: freeing srcprops ?

2007/1/29, Han-Wen Nienhuys [EMAIL PROTECTED]: Neil Jerram escreveu: Kevin Ryde [EMAIL PROTECTED] writes: Han-Wen Nienhuys [EMAIL PROTECTED] writes: why use a separate storage pool for srcprop objects? At a guess, is it because that they're likely to never need freeing, hence can be laid

  1   2   >