-
Notifications
You must be signed in to change notification settings - Fork 27
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
ERROR: -g user:main: Syntax error: Operator expected #122
Comments
Similar problem here: With --debug-info it shows: With --trace it shows: Same happens if I trace or debug the xsd that normally works. With --debug-info or --trace I get the error messages and an empty json. After deleting the empty file and rerun the command without flags, it works again. For the second xsd that never works I get no hint what could be wrong with it. It has a dependency to another xsd that has a dependency to a third xsd. Could this be the reason? Thanks in advance for your help. |
Hm, we should first try to get |
I installed it as a global module. |
What version of SWI-Prolog are you using? (simply call |
SWI-Prolog version 8.0.3 for x64-win64 |
I think the problem here is the Windows OS. Actually, I never tried xsd2json on a Windows machine, but I see several possibilities for issues here. As I don't have a Windows machine at hand, I unfortunately can't provide an ad-hoc solution. @joncorrin, are you using a Windows machine, too? |
I finally managed to install it on my ancient Mac, but not as a global module. Running with debug-info gives me a json file with this content (but nothing in the terminal): Tracing option seems to work, it gives me a huge amount of output in the Terminal. I didn't have the time to check this, but last line is: This may give you a hint? |
I keep getting the following error when trying to convert my xsd file:
ERROR: -g user:main: Syntax error: Operator expected
Seems to be a Prolog issue. Any idea what could be wrong? The XSD appears to be valid.
https://xilo-s3.s3-us-west-2.amazonaws.com/ezauto.xsd
The text was updated successfully, but these errors were encountered: