[IronPython] Parser is not accessible anymore in IP2A6

[Martin Maly]

Yes, Parser being internal definitely causes the error. It is a good question whether it is a permanent change because there are pros and cons going both ways. Let me open a bug on this since it is something we need to make decision on. In the meantime, as a temporary workaround (emphasizing the temporary workaround) you can use -X:PrivateBinding flag with IronPython to get access to the internal/private classes.

The bug I opened is here:

http://www.codeplex.com/IronPython/WorkItem/View.aspx?WorkItemId=14105

Feel free to vote/comment on it and also keep an eye on it for the ultimate resolution.

Thanks for the feedback!
Martin


-----Original Message-----
From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of David.Lawler at franke.com
Sent: Tuesday, November 27, 2007 1:19 PM
To: Discussion of IronPython
Subject: [IronPython] Parser is not accessible anymore in IP2A6

Hello,

The example at www.ironpython.info 'The IronPython 2 Parser' does not seem
to work anymore with IP2A6...fails with a NameError: name 'Parser' is not
defined.  I think it fails because Parser is now 'internal'?  The question
I have is: Is this a permanent change - or is there another way to parse
and then have access to the ast?

Thanks,

David
_______________________________________________
Users mailing list
Users at lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com