Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge master #2

Merged
merged 12 commits into from
Mar 4, 2015
Merged

Merge master #2

merged 12 commits into from
Mar 4, 2015

Conversation

longv2go
Copy link
Owner

@longv2go longv2go commented Mar 4, 2015

No description provided.

mblsha and others added 12 commits December 26, 2014 10:46
By default expressions are evaluated in current frame's language.

When stopped inside a Swift function, current language is Swift, and it's invalid to use Objective-C syntax: many Chisel functions break as a result.

Explicitly specify Objective-C++ as expression language when evaluating commands.

However one problem will still persist: it's still impossible to use Swift objects by name in Chisel functions. One needs to first convert object names to id pointers using evaluateExpressionValueInFrameLanguage(), but the lldb code to enable that was committed very recently and is still unavailable in Xcode 6.1.1.
Added print accessibility tree command. Find accessibility element command reworked
Add basic Swift support (requires Xcode 6)
compliments -> complements
Fix spelling error in README
Fixed incorrect usage of global foundElement causing crashes in some searches
longv2go added a commit that referenced this pull request Mar 4, 2015
@longv2go longv2go merged commit 44477a9 into longv2go:master Mar 4, 2015
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants