unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: mikael@djurfeldt.com
Cc: guile-devel@gnu.org
Subject: Re: Scmutils in guile-2.0
Date: Fri, 08 Feb 2013 11:49:54 +0100	[thread overview]
Message-ID: <87y5ezyt9p.fsf@gnu.org> (raw)
In-Reply-To: <CAA2XvwKU6GyJWs9nTDy=UFyrZuPQ5OHriRxfJ=taUuxcY477FA@mail.gmail.com> (Mikael Djurfeldt's message of "Fri, 8 Feb 2013 11:07:23 +0100")

Mikael Djurfeldt <mikael@djurfeldt.com> skribis:

> On Fri, Feb 8, 2013 at 10:54 AM, Ludovic Courtès <ludo@gnu.org> wrote:
>> Mikael Djurfeldt <mikael@djurfeldt.com> skribis:
>>
>>> On Thu, Feb 7, 2013 at 11:00 PM, Ludovic Courtès <ludo@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) Inlinable
>>>> Procedures").
>>>
>>> Sorry, I'm lost.
>>>
>>> Doesn't define-inlinable define a procedure?
>>
>> It does, but it’s equivalent to what some implementations call
>> ‘define-integrable’.
>
> Ludovic---sorry, I'm being dense.  You see, I just by reflex
> interpreted "integrable" as a mathematical term.  But I should have
> reacted against this being defined as a compatibility measure.
>
> What you are saying is that I should use define-inlinable instead of
> define in the definition of define-integrable, right?

Exactly.  Sorry for not making myself clear!

Ludo’.



  reply	other threads:[~2013-02-08 10:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-07 20:46 Scmutils in guile-2.0 Mikael Djurfeldt
2013-02-07 22:00 ` Ludovic Courtès
2013-02-07 23:33   ` Mikael Djurfeldt
2013-02-08  9:54     ` Ludovic Courtès
2013-02-08 10:07       ` Mikael Djurfeldt
2013-02-08 10:49         ` Ludovic Courtès [this message]
2013-02-13 22:10           ` Mikael Djurfeldt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y5ezyt9p.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guile-devel@gnu.org \
    --cc=mikael@djurfeldt.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).