Parsing exception while using 'as' operator
See original GitHub issueI’m trying to use following expression:
string.IsNullOrEmpty(variable as string)
but it results with exception: DynamicExpresso.Exceptions.ParseException: ‘)’ or ‘,’ expected (at index 40).
Adding extra parenthesis as message suggests solves the issue, but the expression is obviously wrong then
string.IsNullOrEmpty(variable as string))
Seems there is something wrong with parser.
Issue Analytics
- State:
- Created 3 months ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Exception thrown when parsing data - java
Edit 1: Problem with the code was that the input was in the format ddMMyyyy(06071994) and the format was dd MM yyyy (should...
Read more >Caught parsing exception during wrapDescribeOperator()
My job is a very basic DB2 connector connecting to an open systems DB2 systems; running SQL contained within a file. The result...
Read more >Parsing and Exceptions - JSON for Modern C++
The parse() function accepts a bool parameter allow_exceptions which controls whether an exception is thrown when a parse error occurs ( true ,...
Read more >Exceptions - Java Programming MOOC
The user input, in this case the string no! , is given to the Integer.parseInt method as a parameter. The method throws an...
Read more >How to Solve Class Cast Exceptions in Java?
This exception is rise automatically by JVM whenever we try to improperly typecast a class from one type to another i.e when we're...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@IAMJDA thanks for narrowing it down! It’s indeed a regression in the way the types are parsed: we don’t reset the parser position properly if the type has no modifier. I’ll need to ensure it’s working for all the possible type modifiers. For example:
but it shouldn’t take too long 🤞
Manual bisect:
#178 seems to be to blame