Hi, First big thanks for yet another great release! However, as I see you haven't addressed this small issue I described a while ago. Please confirm you have received my report and if you are going to address it. Now I've manually added these properties to the PythonSyntaxError class: public class PythonSyntaxError : Exception, ICustomExceptionConversion { int lineNo, columnNo; string lineText, file; public int LineNumber { get { return lineNo; } } public int ColumnNumber { get { return columnNo; } } public string File { get { return file; } } public string LineText { get { return lineText; } } ... } Regards, Szymon Kobalczyk Szymon Kobalczyk napisał(a): Hi, I found it quite convenient to be able to catch parsing error from the engine's Compile method and read the line and column number where the error occurred. In previous version this was simply displayed in the PythonSyntaxError's message. Currently it was removed and instead this exception carries this information in private fields so it can recreate PythonException. Do you have anything against exposing these fields as read-only properties?Regards, Szymon Kobalczyk _______________________________________________ users mailing list users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com --
|
_______________________________________________ users mailing list users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com