[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ReactOS: stack vs heap
From: |
Werner LEMBERG |
Subject: |
Re: ReactOS: stack vs heap |
Date: |
Tue, 05 Sep 2023 06:12:06 +0000 (UTC) |
> Thanks. One thing I don't understand, is the "+ 2" in the code below:
>
> AF_LatinBlue blue_sorted[AF_BLUE_STRINGSET_MAX_LEN + 2];
>
> for ( i = 0; i < axis->blue_count; i++ )
> blue_sorted[i] = &axis->blues[i];
>
> If that + 2 is correct to be there, then we need a similar + 2 in
> aflatin.h for blues. But I cannot see why it's needed.
Good catch! This is due to a synchronization error between FreeType
and ttfautohint: I've originally developed the code for ttfautohint,
which adds two artificial blue zones, then imported it back into
FreeType, where I forgot to adjust the array size accordingly.
Now fixed in git, thanks.
Werner
- Re: ReactOS: stack vs heap, (continued)
- Re: ReactOS: stack vs heap, Alexei Podtelezhnikov, 2023/09/01
- Re: ReactOS: stack vs heap, Werner LEMBERG, 2023/09/01
- Re: ReactOS: stack vs heap, Ben Wagner, 2023/09/01
- Re: ReactOS: stack vs heap, Alexei Podtelezhnikov, 2023/09/01
- Re: ReactOS: stack vs heap, Behdad Esfahbod, 2023/09/04
- Re: ReactOS: stack vs heap, Behdad Esfahbod, 2023/09/04
- Re: ReactOS: stack vs heap, Behdad Esfahbod, 2023/09/04
- Re: ReactOS: stack vs heap, Behdad Esfahbod, 2023/09/04
- Re: ReactOS: stack vs heap, Werner LEMBERG, 2023/09/04
- Re: ReactOS: stack vs heap, Behdad Esfahbod, 2023/09/05
- Re: ReactOS: stack vs heap,
Werner LEMBERG <=
Re: ReactOS: stack vs heap, Oliver Brunner, 2023/09/01