-
Notifications
You must be signed in to change notification settings - Fork 560
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
perl -MO=BACKEND file.pl appears to not function in 5.005_62 #787
Comments
From bkuhn@ebb.orgMy humblest apologies if I am reporting something that is already known. I I have been having a problem using Backends via the O module in 5.005_62. I $ ./perl -I lib -MO=Bytecode t/base/cond.t > x On 5.005_61, configured the same way on the same system, both perl commands I discovered the problem while working on my own backend (which works fine I have confirmed that the O module is calling compile() from the appropriate This simple example exhibits it: place this file in foo/B/TestProblem.pm sub compile { return sub { print "Never gets here\n"; } Then try: $ perl5.00562 -Ifoo -MO=TestProblem some_script.pl I am sorry that I cannot give any more information on the specifics of the Thanks, and again, sorry if this is already a known bug. Perl Info
|
From @gsarOn Tue, 26 Oct 1999 02:54:36 EDT, "Bradley M. Kuhn" wrote:
When it doubt, look up the p5p archives. http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/1999-10/msg00652.html Sarathy |
From [Unknown Contact. See original ticket]Gurusamy Sarathy wrote:
Sarathy, my apologies. I did a search, but it clearly wasn't extensive I read the threads in question. It appears that your STOP {} block solution (It wasn't clear from the thread in question if this would be the pursued |
From @gsarOn Thu, 04 Nov 1999 01:32:25 EST, "Bradley M. Kuhn" wrote:
I think so, unless there are objections from others.
Since I proposed the idea, I think it's on my plate, but I wouldn't Doing it should be very simple--add a PL_stopav, push CVs onto it Sarathy |
Migrated from rt.perl.org#1714 (status was 'resolved')
Searchable as RT1714$
The text was updated successfully, but these errors were encountered: