[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: macOS/GCC support policy (was: [PATCH v5] Enable xwidgets on macOS)
From: |
Noam Postavsky |
Subject: |
Re: macOS/GCC support policy (was: [PATCH v5] Enable xwidgets on macOS) |
Date: |
Thu, 1 Aug 2019 22:22:40 -0400 |
On Thu, 1 Aug 2019 at 17:40, Alan Third <address@hidden> wrote:
> > > > > Anyway, the code contains two calls to
> > > > > evaluateJavaScript:completionHandler: which is a problem as we’re
> > > > > banned from using ObjC blocks, and the completion handler is an ObjC
> > > > > block. Unless GCC supports them now, which I doubt.
> I found the previous thread about removing them from macfont.m:
>
> https://lists.gnu.org/archive/html/bug-gnu-emacs/2017-12/msg00301.html
If the API requires blocks, I guess they have some stable ABI. Is it
not possible to construct a block at runtime, as a plain C struct?
- macOS/GCC support policy (was: [PATCH v5] Enable xwidgets on macOS), Alan Third, 2019/08/01
- Re: macOS/GCC support policy (was: [PATCH v5] Enable xwidgets on macOS),
Noam Postavsky <=
- Re: macOS/GCC support policy, Eli Zaretskii, 2019/08/02
- Re: macOS/GCC support policy, Philipp Stephani, 2019/08/02
- Re: macOS/GCC support policy, Eli Zaretskii, 2019/08/02
- Re: macOS/GCC support policy, Alan Third, 2019/08/03
- Re: macOS/GCC support policy, Eli Zaretskii, 2019/08/03
- Re: macOS/GCC support policy, Alan Third, 2019/08/03