lua-users home
lua-l archive

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

I don't know. But I do know that it definitely makes bridges between
foreign languages and Swift much more difficult (if not impossible).
Transpiling is not out of the question, but it also seems unnecessary
to me personally.

On Thu, Jul 10, 2014 at 9:56 PM, Jay Carlson <> wrote:
> On Jul 10, 2014 10:10 PM, "Steven Degutis" <> wrote:
>> I understand where you're coming from in wanting
>> more flexibility in the API and in Lua itself. I especially understand
>> it having written a few ObjC bridges myself, being no stranger to
>> NSInvocation and family.
>> I'm also quite disillusioned about such bridges in the first place,
>> having come to the same conclusion that Apple apparently has (as
>> they've deprecated all bridges and made NSInvocation inaccessible via
>> Swift), namely that bridges between even mildly disparate programming
>> languages are inherently broken and should be avoided except in the
>> rarest of prototypical cases.
> Do you think discouraging NSInvocation is to make static analysis easier? If
> so, would this have an impact on the App Store control process?
> Jay