dynoplibs in core or no?
julian.notfound at gmail.com
Wed Jun 2 05:49:27 UTC 2010
> Not to be a pest, but the "open" opcode becoming a dynop is what broke
> PL/Parrot recently. There is nothing wrong with open being a dynop per
> se, but a long standing bug with dynops that rarely got tickled is now
> much more important. If that bug was fixed, "open" being a dynop would
> be all gravy.
This one can be easily fixed just by not using open. Just create a new
'FileHandle' and use its 'open' method.
More information about the parrot-dev