-
Notifications
You must be signed in to change notification settings - Fork 0
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
Nested if statements / curly braces cause issues with compiler (iOS) #143
Comments
Note: there was talk on discord regarding nested ifs being "fixed" in Open-Jellycore. I have verified that the program below, compiles without syntax errors in Open-Jellycore |
simplier program shows the same syntax error |
We can't use open jellycore in iOS though, can we? |
Open-Jellycore is used by Open-Jellycuts https://github.com/openjelly/open-jellycuts an iOS app. That said, Open-Jellycuts is far behind the AppStore version of Jellycuts, and you would be likely to encounter many other issues of things that work in Jellycuts but don't work in Open-Jellycuts. My comments intended as context for whomever was going be fixing the nested if issue and has access to both source code bases. |
Is there any updates in this? :) |
Not that I've seen. As mentioned above, it's not an issue in Open Jelly, but that doesn't really help the rest of us until Open Jelly gets up to speed. The other issues I've been running into with JellyCuts makes it hard to use as a way to build shortcuts. Hoping for some fixes soon. If you have other issues you've noticed, please do make an issue for them in this repo. You can also provide info to me, as I am helping them compile some other issue notes as well. |
Describe the bug
when nesting if statements or other items that have curly braces, the compiler gets confused and is looking for RegEx
To Reproduce
Steps to reproduce the behavior:
Expected behavior
compiling should happen without issue with nested if statements
Screenshots
Information
Device: iPhone 14
OS: 17.5.1
Jellycuts Version: 2.3(0)
Jailbroken? No
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: