You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After discussing with @JonesMB, there are two main concerns:
There are no native namespaces. Everything is global, so although you can directly import files, you can't have any naming conflicts.
It's standard (and, in some cases, necessary) to split files into .h and .m in C/C++ form. Lovely.
1 is doable, and likely necessary for PHP.
2 will require an Objective C-specific secondary compiler step. It'll need to go through every generated class (.m) and generate the corresponding .h.
The text was updated successfully, but these errors were encountered:
After discussing with @JonesMB, there are two main concerns:
.h
and.m
in C/C++ form. Lovely.1 is doable, and likely necessary for PHP.
2 will require an Objective C-specific secondary compiler step. It'll need to go through every generated class (
.m
) and generate the corresponding.h
.The text was updated successfully, but these errors were encountered: