open(STDOUT, '>>', 'sbguioutput.txt') or die "Can't open log"; # Regul
+ar Output
open(STDERR, '>>', 'sbguierror.txt') or die "Can't open log"; # Error
+ Output
My guess is file permissions? Thanks!
| [reply]
[d/l] |
open(STDOUT, '>>', 'sbguioutput.txt') or die "Can't open log:$!"; #
+Note $! added
FYI -MAD info from http://perldoc.perl.org/perl594delta.html#MAD
MAD, which stands for Misc Attribute Decoration, is a still-in-development work leading to a Perl 5 to Perl 6 converter. To enable it, it's necessary to pass the argument -Dmad to Configure. The obtained perl isn't binary compatible with a regular perl 5.9.4, and has space and speed penalties; moreover not all regression tests still pass with it.
When in doubt, mumble; when in trouble, delegate; when in charge, ponder. -- James H. Boren
| [reply]
[d/l] |
| [reply] |
So, it looks like you (PilotinControl) have a perl configured with -Dmad. ("To enable it, it's necessary to pass the argument -Dmad to Configure.".) This is an esoteric option related to source code transformation; you must have enabled it somehow.
Perhaps you were interested in P6 years ago and installed or configured something related to that? Or perhaps you've installed some automated refactoring thing?
Then again, I don't know how that could/would carry over from your XP setup to your Win 7 setup.
Given that MAD normally creates a bunch of overhead (making perl run more slowly and use more memory) and typically doesn't provide any benefit, you should figure out how to switch it off. As a bonus, that should fix your problem too.
If you decide to leave MAD on, then I think you need to figure out in to which directory perl writes the file specified in PERL_XMLDUMP. Does the perl process you're running have permission to write to that directory? Windows 7 tightened up permissions considerably compared to XP.
Hth.
Not that it's relevant to the OP, but for completeness sake, from #perl6 log, Aug 22, 2013:
17:14 TimToady well, I'm not necessarily recommending the MAD approach these days,
since it turned out to be rather fragile
While Larry has previously suggested it was best to leave the MAD code and configure option in perl5 core for the time being, I think that suggestion is now somewhat stale. In the above log Larry (quite sensibly imo) suggests one day leveraging FROGG's v5 for translation. Such a translator would not use MAD. Also, fglock started a perlito based translator a couple months back -- and it won't use MAD either. Finally, in August (and the above IRC log) Util talked about creating a translator (Blue_Tiger) that could theoretically use MAD -- but he said he thought PPI was good enough.
| [reply] |
| [reply] |
Ugh. I really do want to help. But I'm going to need information you're not providing.
Let's see if I can steer this in a more effective direction. :)
You indicate you used to be on XP, but now you're on Windows 7.
That's nice, but tell's me nothing about the Perl on XP, nor on your Windows 7.
Did you upgrade XP to Windows 7? Did Windows upgrade also upgrade Perl?
No? Then did you upgrade Perl on Windows 7? If so. How did you do it?
Starting to catch my drift now? :)
Did you install Perl on Windows 7? What Perl did you install/upgrade; Strawberry? ActivePerl? What version?
The more information you can provide. The better we can help. There is no such thing as too much information. :)
I'll keep watching, in hopes you'll have some better information to go on. :)
Best wishes.
--Chris
Hey. I'm not completely useless. I can be used as a bad example.
| [reply] |
| [reply] |