iOS Compilation Changes #2
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
August 16, 2011 12:37
Alternate version of FSNSValue for iOS. Alternate version of FSMethod for iOS -- which likely doesn't work right. Barebones iOS app -- enter an fscript expression into the textfield, see the result in the textview below. libffi for iphone (device+simulator)
Don't use result if isOK == NO, instead use the errorMessage.
|
Looks great. Philippe Le 16 août 2011 à 22:31, pablomarx a écrit :
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The vast majority of the changes are simple -- Foundation import instead of AppKit, avoiding NSPoint/NSRect/NSSize on iOS (#if TARGET_OS_IPHONE).
Bulk of the change set is including an iOS compatible libffi (from https://github.com/parmanoir/jscocoa/ ).
FSMethod required changes as NSMapTable doesn't exist -- I've made a separate copy of this for iOS, as I'm not entirely sure about the changes.
NSAllocateCollectable and siblings don't exist -- So they were implemented in iOS-glue, behaving as I believe these would on a non-GC system.