Hi Rob,
My personal view is that it would be great to include this.
I guess the main underlying question is how "bloated" we want to make the
distribution. Your contribution is just 200 lines, so I think it is fine.
Of course, if we always say that...
My personal wish would be to have something
Hi Maxime,
On Fri, Dec 20, 2024 at 4:15 PM Maxime Devos wrote:
> > Thanks for your patches! Applied now.
>
>
>
> Regardless of the question whether to generalise, there was also the thing
> about the test testing for returning #true even though this behaviour isn’t
> documented anywhere.
>
Mayb
Adam,
Thanks for your patches! Applied now.
Best regards,
Mikael
g and ambiguous (c.f.
"input") and would replace it with "from-port" to conform with other
procedure names (such as with-input-from-port). On the other hand,
"line-in-file" feels natural despite the existence of with-input-from-file.
On Tue, Dec 17, 2024 at 8:21 AM Mikael Dju
Do others think this as well? To me, the shorter names which Adam selected
seem more palatable. Otherwise they get a bit long.
Den tis 17 dec. 2024 06:11Nala Ginrut skrev:
> The preferred activity in your design is more like for-each family, say,
> handle the result inside the proc without retur
Since commit 7379049d3, Guile is no longer bootstrapping. (Thanks to dsmith
and rlb in the chat.)
It turns out that the bad commit is solely 7379049d3 and the rest seem OK,
so I've prepared a patch to fix this. (I can commit it to main, but I
thought commit history will look nicer if Andy fixes th
I just committed a module (oop goops keyword-formals) for users who prefer
not to switch between define-method and define-method*.
If you do
(use-modules (oop goops) (oop goops keyword-formals))
you'll get a define-method which takes keyword formals.
Best regards,
Mikael
Sorry for all spam, but I realize that R6RS does this better:
(import (rename (except (oop goops) define-method) (define-method*
define-method)))
Maybe we should have a #:rename ((ORIG . SEEN) ...) in the Guile native
module system? Or perhaps we should gradually move over to R6RS?
Best regards,
Den tis 26 nov. 2024 00:51Mikael Djurfeldt skrev:
> On Fri, Nov 22, 2024 at 1:20 PM wrote:
>
>> ...which I think in your version, not having to use define-method*
>> feels more elegant/GOOPSy to me, as it's all overloads/generics,
>> but I have no strong opionion on this.
>>
>
> There's actually
On Fri, Nov 22, 2024 at 1:20 PM wrote:
> ...which I think in your version, not having to use define-method*
> feels more elegant/GOOPSy to me, as it's all overloads/generics,
> but I have no strong opionion on this.
>
There's actually a secret to what I have committed:
define-method* *is* the d
I just pushed this to Savannah.
On Mon, Nov 25, 2024 at 11:28 AM Mikael Djurfeldt
wrote:
> This is the third attempt at introducing keyword aware methods in GOOPS.
>
> What is new in v3 is that keyword arguments and default parameters to
> keyword arguments are handled correctl
This is the third attempt at introducing keyword aware methods in GOOPS.
What is new in v3 is that keyword arguments and default parameters to
keyword arguments are handled correctly when using (next-method). Now only
those keyword arguments actually present in a call get forwarded to the
next-met
Ah... I forgot to complete parse-keyword-formals, which is currently only
rudimentary and doesn't compose the correct argument list for (next-method).
There will be a version 3...
On Sun, Nov 24, 2024 at 3:43 PM Mikael Djurfeldt
wrote:
> Guile maintainers might want to consider if w
Guile maintainers might want to consider if we should time this kind of
change in the API with a particular release. For my part, I think we could
just add it.
On Sun, Nov 24, 2024 at 3:40 PM Mikael Djurfeldt
wrote:
> This is my second attempt at introducing keyword aware methods in GO
This is my second attempt at introducing keyword aware methods in GOOPS.
I was split but finally decided to go with keeping keyword non-aware
define-method and method and introducing keyword aware new syntax method*
and define-method*. Arguments are:
1. It preserves simplicity in method and defin
(It's (define-method (f #:key foo) ...).)
This is a valid point. Certainly there should be unambiguous rules so that
we know which method should be selected. (I planned to examine this aspect
before applying my patch to Guile. I was just eager to share what I had
done in order to collect opinions
Hi Maxime,
Well, these particular examples aren't valid since GOOPS doesn't allow type
specifiers for keyword arguments. (It's the same in CLOS.) Type dispatch is
done *only* on the required arguments.
Best regards,
Mikael
On Sat, Nov 23, 2024 at 4:31 PM Maxime Devos wrote:
> >Any opinions on
e in this
recommendation is 90%, given that the Guile precedent is a strong argument
for following suit.
4o
On Fri, Nov 22, 2024 at 1:29 PM Mikael Djurfeldt
wrote:
> Thanks!
>
> See responses to Tomas.
>
> On Fri, Nov 22, 2024 at 1:20 PM wrote:
>
>> Mikael D
Thanks!
See responses to Tomas.
On Fri, Nov 22, 2024 at 1:20 PM wrote:
> Mikael Djurfeldt writes:
>
> Hello,
>
> > That was elegant. :-)
>
> :)
>
> > Nope---haven't seen it. (Or, at least I do not remember it.)
> >
> > Maybe I should hav
Hi Tomas,
Thank you for your feedback. Answers below.
On Fri, Nov 22, 2024 at 12:46 PM Tomas Volf <~@wolfsden.cz> wrote:
> I do find the symmetry between define-method/define-method* and
> define/define* pleasing.
>
Yes, I guess we are free to form GOOPS in our own style regardless of CLOS.
>
at is best: Having a define-method* or having the
functionality in define-method itself?
Best regards,
Mikael
On Thu, Nov 21, 2024 at 11:00 PM wrote:
> Mikael Djurfeldt writes:
>
> Hi Mikael,
>
> > Since there are no comments, I'm inclined to apply this patch. I will do
&
(I will of course add proper documentation in the manual, etc.)
On Thu, Nov 21, 2024 at 9:33 PM Mikael Djurfeldt
wrote:
> Since there are no comments, I'm inclined to apply this patch. I will do
> that on Sunday if there are no comments before that.
>
> Maybe I should first
e, Nov 19, 2024 at 5:41 PM Mikael Djurfeldt
wrote:
> Hi all,
>
> I've implemented support for keyword arguments (corresponding to define*
> and lambda*) in GOOPS. The functionality is similar to that of CLOS (which
> also has keyword in methods) in that dispatch is not done on
Hi all,
I've implemented support for keyword arguments (corresponding to define*
and lambda*) in GOOPS. The functionality is similar to that of CLOS (which
also has keyword in methods) in that dispatch is not done on the keyword
part.
You can find the changes in the goops-keyword branch at
https:
I think the wording in the Guile manual is unfortunate.
What RnRS says is that an identifier which is bound to a location is a
variable.
What the Guile manual is then discussing is our implementation details of
this, where "bound" is used in a different sense than in RnRS.
Den tors 14 nov. 2024
Hi Tommi,
I haven't seen it discussed and don't rule out that it could have some
value, if suitable space still exists in the current SCM encoding of types.
Personally, though, my hopes are that eventually most actual computation in
Guile code would be done unboxed---which is a compilation proble
Hi all,
I've come to the conclusion that this problem is unsolvable and I will
abandon the idea of an at-exit-hook. The most serious potential consequence
of running it in really_cleanup_for_exit(), which is indirectly invoked
through atexit(), is that the resources to clean up or the Guile librar
OK, so people have brought up two issues:
1. It is for various reasons not recommended to call atexit() from a
dynamically linked library (which Guile already does before my suggested
change, n.b.).
2. It is not async signal safe.
A suggested remedy would then be:
Instead of calling the at-exit
Hi,
I think it would be good to have an at-exit-hook which is run atexit(). The
motivation is that Guile can provide bindings for libraries which may want
to clean up resources at exit. If the at-exit-hook exists, this would then
be one way to make sure that the linked in library can do this at ex
Dear Daphne,
What you propose sounds exciting! I also think that you have the right
background to pull this off in a nice way.
Obviously, Andy Wingo should give his view on this, but I thought that
your message should have some response. :-)
Best regards,
Mikael Djurfeldt
On Tue, Sep 10, 2024
Your two points sound good.
However, I personally hope that Guile will continue to be friendly towards
those using it as an embedded language. There, a C API is important. There
*is* a downside in moving to Scheme from that perspective, but that is fine
as long as it is easy to call Scheme from C.
ou will have of it.
>
> 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
>> > > sk
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, ha
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
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 :-)
> > >
> >
> >
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
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 possible
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 manua
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
>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 th
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 lan
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 function
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 d
(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 projects
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 pi
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-
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
> e
(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
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 importa
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
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, th
c f)
>>> (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:
>>>
>>>>
(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 checking.
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 details
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 snapsho
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 fas
Stefan Israelsson Tampe <
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
13:18, Mikael Djurfeldt writes:
>
> > 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
>
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
expressi
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 R
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,
Mikae
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
For what it's worth:
Then I of course retract what I said about RMS not showing good leadership
by not consulting with Andy and Ludovic. I still support the initiative to
find a new governing structure for GNU. Note also that both the GNU
maintainers statement and RMS himself talk about new govern
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 h
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 thi
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 rem
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?
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 language.
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
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
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.
>
> Ge
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.
>>
>> Also, w
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.
>
> Also, while in theory quite nice it has the problem that
> Guile is really slow in restoring continuations, d
On Fri, Nov 2, 2018 at 2:35 PM Mikael Djurfeldt
wrote:
> Given this situation, is there still a way to use the module system to
> give (ice-9 match) $ precedence? There is. Göran Weinholt has pointed out
> that other Scheme implementations tend to export their auxilliary keywords.
>
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 9
I've looked a little at the Guile vm and compiler.
What a beautiful work! It also has very nicely written documentation. Very
impressive!
Here's an idea/question:
SICP describes a register machine with a stack discipline which is
different from most machine models in that it doesn't have a call
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. :-)
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 inste
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
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 &#
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
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 be
suggestion and give comments or an OK.
Best regards,
Mikael Djurfeldt
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 t
eased
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 e
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. Yo
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 and psyntax-pp.go before the rest
of the .go files so that they are handled by a fast macro expander. This
saves time for a
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 to
ching 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
;;
st regards,
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) algori
t; ** Remove "self" field from vtables and "redefined" field from classes
>
> These fields were used as part of the machinery for class redefinition
> and is no longer needed.
>
> ** VM hook manipulation simplified
>
> The low-level mechanism to instrument a
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.
>
Yes, but I ima
ld be supplemented by run-time
invocation statistics to make better choices of what to instantiate and
compile---as is being done in several interpreters/compilers.
Den 9 jan 2018 15:30 skrev "Mikael Djurfeldt" :
> Hi,
>
> Hi think this is a marvelous development and, for what it's wo
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
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 us
voided by 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
[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
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 t
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 wrote:
Is there an easy way to replace the bootstrap interpreter with an already
built Guile in order to speed up the build process?
1 - 100 of 170 matches
Mail list logo
