[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Rational
From: |
Hans Åberg |
Subject: |
Re: Rational |
Date: |
Wed, 23 May 2018 18:22:12 +0200 |
> On 23 May 2018, at 18:12, David Kastrup <address@hidden> wrote:
>
> Hans Åberg <address@hidden> writes:
>
>> I ended up using GC_malloc_uncollectable, because it turned out too
>> tricky to use malloc.
>
> This is C++, so we basically end up with operator ::new and operator
> ::delete unless overriden by individual classes. They use
This what they suggest for the Boehm GC, and it is what caused problems in my
program.
> ...the
> equivalent of GC_malloc_uncollectable.
So what exactly is this in the Boehm GC?
>> And I found no reference to it in LilyPond, so I got curious about how
>> you do it. But you are not going to tell me, so forget about it.
>
> You know, if you actually bothered _asking_, you'd increase your chances
> of getting an answer.
Typically when the item is brought up people would say "Yes, we use this or
that", rather than long bodies of text with no such information.
- Re: Rational, (continued)
- Re: Rational, Hans Åberg, 2018/05/23
- Re: Rational, David Kastrup, 2018/05/23
- Re: Rational, Hans Åberg, 2018/05/23
- Re: Rational, David Kastrup, 2018/05/23
- Re: Rational, Hans Åberg, 2018/05/23
- Re: Rational, David Kastrup, 2018/05/23
- Re: Rational, Hans Åberg, 2018/05/23
- Re: Rational, David Kastrup, 2018/05/23
- Re: Rational, Hans Åberg, 2018/05/23
- Re: Rational, David Kastrup, 2018/05/23
- Re: Rational,
Hans Åberg <=
- Re: Rational, David Kastrup, 2018/05/23
- Re: Rational, Hans Åberg, 2018/05/23
- Re: Rational, David Kastrup, 2018/05/23
- Re: Rational, Hans Åberg, 2018/05/23
- Re: Rational, David Kastrup, 2018/05/23
- Re: Rational, Hans Åberg, 2018/05/23
- Re: Rational, Kieren MacMillan, 2018/05/23
- Re: Rational, metachromatic, 2018/05/26
- Re: Rational, David Kastrup, 2018/05/26
- Re: Microrhythm, Hans Åberg, 2018/05/22