Menu
▾
▴
expectperl-discuss
|
From: Blackstone, J. D. <jda...@ci...> - 2002-06-05 13:12:54
|
Judging by the problem with "qr," I'm guessing Expect.pm will not work with any Perl earlier than 5.005 (or is it 5.6?) which introduced the qr// syntax for compiling regular expressions and passing them around as reusable values. Even if the module itself ran under an earlier Perl, I'm guessing you wouldn't find it near as useful without this syntax. 5.004 is several years old; I'd hammer my sysadmin with this and beg them to upgrade. :) jdb > -----Original Message----- > From: ex...@ih... [mailto:ex...@ih...] > Sent: Tuesday, June 04, 2002 7:46 PM > To: exp...@li... > Subject: [Expectperl-discuss] perl 500404 with Expect 1.15 > > > Apologies if this is mentioned somewhere. I did look > in the readme and the man page. Does expect > work with perl 5.00404? I am having some > problems. expect spawn is hanging > the test.pl didn't run: > > perl test.pl > 1..36 > Bareword "qr" not allowed while "strict subs" in use at > test.pl line 270. > syntax error at test.pl line 270, near "/^" > Bareword "prompt" not allowed while "strict subs" in use at > test.pl line > 270. > Global symbol "self" requires explicit package name at > test.pl line 270. > Substitution pattern not terminated at test.pl line 276. > > > _______________________________________________________________ > > Don't miss the 2002 Sprint PCS Application Developer's Conference > August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm > > _______________________________________________ > Expectperl-discuss mailing list > Exp...@li... > https://lists.sourceforge.net/lists/listinfo/expectperl-discuss > |
|
From: <RGi...@a1...> - 2002-06-05 15:33:28
|
> Apologies if this is mentioned somewhere. I did look > in the readme and the man page. Does expect > work with perl 5.00404? I am having some > problems. expect spawn is hanging > the test.pl didn't run: I'm not sure. I think that Expect.pm is 5.004 clean (not using anything from 5.005), but test.pl is definitely not, as I only recently added some tests (using the qr// syntax). I'm sure that it would be easy to just go through test.pl and remove/revert the offending syntax. Alternatively you could simply install Expect.pm and hope the best. As I do not use autoload and the compilation of Expect.pm obviously succeeded, it should be OK from a sytactical point of view. But don't ask me about semantical changes between 5.004 and 5.005... Hope this helps, Roland -- RGi...@cp... |
|
From: Blackstone, J. D. <jda...@ci...> - 2002-06-07 13:55:09
|
> -----Original Message----- > From: ex...@ih... [mailto:ex...@ih...] > Sent: Thursday, June 06, 2002 7:35 PM > To: Blackstone, J. David > Cc: exp...@li... > Subject: Re: perl 500404 with Expect 1.15 ... > It looks like my problems are in Expect with spawn > these lines seem to be where things just hang: > > 144 open(STDIN,"<&". $slv->fileno()) > 147 open(STDOUT,">&". $slv->fileno()) > 150 open(STDERR,">&". $slv->fileno()) > > Okay maybe I'm SOL but maybe someone has a hunch on what > the problem is??? I think that is fairly new syntax as well. I was trying something like that recently in an unrelated program and had trouble making it work, but I don't remember if it was because it was an older perl. > > 5.004 is several years old; I'd hammer my sysadmin with > this and beg them > > to upgrade. :) > > If only life were so simple....I have the power to perform the upgrade > but there are dependencies on this perl. I don't know what > they are.... Oh, ho, ho. :) You need my super-special means of running many perls at once trick. Compile with --prefix=/usr/local/perl561. Make symlinks from everything in /usr/local/perl561/bin EXCEPT /usr/local/perl561/bin/perl into /usr/local/bin. Then write your programs explicitly with: #!/usr/local/bin/perl5.6.1 or #!/usr/[local/]?bin/perl5.00502 Then your programs don't break on upgrades and you can easily remove a version as a unit if and when you upgrade all programs that used it. jdb |
|
From: <ex...@ih...> - 2002-06-07 17:37:51
|
Blackstone, J. David writes: > > >> -----Original Message----- >> From: ex...@ih... [mailto:ex...@ih...] >> Sent: Thursday, June 06, 2002 7:35 PM >> To: Blackstone, J. David >> Cc: exp...@li... >> Subject: Re: perl 500404 with Expect 1.15 > > ... > >> It looks like my problems are in Expect with spawn >> these lines seem to be where things just hang: >> >> 144 open(STDIN,"<&". $slv->fileno()) >> 147 open(STDOUT,">&". $slv->fileno()) >> 150 open(STDERR,">&". $slv->fileno()) >> >> Okay maybe I'm SOL but maybe someone has a hunch on what >> the problem is??? > > I think that is fairly new syntax as well. I was trying something like > that recently in an unrelated program and had trouble making it work, but I > don't remember if it was because it was an older perl. > >> > 5.004 is several years old; I'd hammer my sysadmin with >> this and beg them >> > to upgrade. :) >> >> If only life were so simple....I have the power to perform the upgrade >> but there are dependencies on this perl. I don't know what >> they are.... > > Oh, ho, ho. :) You need my super-special means of running many perls at > once trick. Compile with --prefix=/usr/local/perl561. Make symlinks from > everything in /usr/local/perl561/bin EXCEPT /usr/local/perl561/bin/perl into > /usr/local/bin. Then write your programs explicitly with: > #!/usr/local/bin/perl5.6.1 > or > #!/usr/[local/]?bin/perl5.00502 > > Then your programs don't break on upgrades and you can easily remove a > version as a unit if and when you upgrade all programs that used it. I must be missing something obvious.... How will this co-exist with the the current /usr/local/bin/perldoc etc.?? |
|
From: Roland G. <RGi...@CP...> - 2002-06-10 19:41:33
|
> >> If only life were so simple....I have the power to perform the upgrade > >> but there are dependencies on this perl. I don't know what > >> they are.... > > > > Oh, ho, ho. :) You need my super-special means of running many perls at > > once trick. Compile with --prefix=/usr/local/perl561. Make symlinks from > > everything in /usr/local/perl561/bin EXCEPT /usr/local/perl561/bin/perl into > > /usr/local/bin. Then write your programs explicitly with: > > #!/usr/local/bin/perl5.6.1 > > or > > #!/usr/[local/]?bin/perl5.00502 > > > > Then your programs don't break on upgrades and you can easily remove a > > version as a unit if and when you upgrade all programs that used it. > > I must be missing something obvious.... How will this co-exist > with the the current /usr/local/bin/perldoc etc.?? Well, it won't. But as you won't be doing development under the old perl, you won't need its user dpcumentation, i.e. the old perldoc. The same goes for perlbug and perlcc (probably). So you can replace those three with the new version. Alternatively you might consider changing all the #! lines in the old scripts to point at perl5.00404 instead of just perl. Hope this clears things up. Roland |
|
From: <ex...@ih...> - 2002-06-11 01:33:58
|
On Mon, 10 Jun 2002 21:41:20 +0200 Roland Giersig <RGi...@CP...> wrote: > > >> If only life were so simple....I have the power to perform the > > >> upgrade but there are dependencies on this perl. I don't know what > > >> they are.... > > > > > > Oh, ho, ho. :) You need my super-special means of running many > > > perls at once trick. Compile with --prefix=/usr/local/perl561. > > > Make symlinks from everything in /usr/local/perl561/bin EXCEPT > > > /usr/local/perl561/bin/perl into/usr/local/bin. Then write your > > > programs explicitly with:#!/usr/local/bin/perl5.6.1 > > > or > > > #!/usr/[local/]?bin/perl5.00502 > > > > > > Then your programs don't break on upgrades and you can easily > > > remove a version as a unit if and when you upgrade all programs > > > that used it. > > > > I must be missing something obvious.... How will this co-exist > > with the the current /usr/local/bin/perldoc etc.?? > > Well, it won't. But as you won't be doing development under the old > perl, you won't need its user dpcumentation, i.e. the old perldoc. The > same goes for perlbug and perlcc (probably). So you can replace those > three with the new version. Alternatively you might consider changing > all the #! lines in the old scripts to point at perl5.00404 instead of > just perl. For now the new scripts will point to the new perl, thanks for the ideas. > > Hope this clears things up. > > Roland |
|
From: <ex...@ih...> - 2002-06-07 00:29:40
|
Blackstone, J. David writes: > Judging by the problem with "qr," I'm guessing Expect.pm will not work > with any Perl earlier than 5.005 (or is it 5.6?) which introduced the qr// > syntax for compiling regular expressions and passing them around as reusable > values. Even if the module itself ran under an earlier Perl, I'm guessing > you wouldn't find it near as useful without this syntax. quotemeta is new too I found out (test.pl only though) It looks like my problems are in Expect with spawn these lines seem to be where things just hang: 144 open(STDIN,"<&". $slv->fileno()) 147 open(STDOUT,">&". $slv->fileno()) 150 open(STDERR,">&". $slv->fileno()) Okay maybe I'm SOL but maybe someone has a hunch on what the problem is??? > > 5.004 is several years old; I'd hammer my sysadmin with this and beg them > to upgrade. :) If only life were so simple....I have the power to perform the upgrade but there are dependencies on this perl. I don't know what they are.... > > jdb > >> -----Original Message----- >> From: ex...@ih... [mailto:ex...@ih...] >> Sent: Tuesday, June 04, 2002 7:46 PM >> To: exp...@li... >> Subject: [Expectperl-discuss] perl 500404 with Expect 1.15 >> >> >> Apologies if this is mentioned somewhere. I did look >> in the readme and the man page. Does expect >> work with perl 5.00404? I am having some >> problems. expect spawn is hanging >> the test.pl didn't run: >> >> perl test.pl >> 1..36 >> Bareword "qr" not allowed while "strict subs" in use at >> test.pl line 270. >> syntax error at test.pl line 270, near "/^" >> Bareword "prompt" not allowed while "strict subs" in use at >> test.pl line >> 270. >> Global symbol "self" requires explicit package name at >> test.pl line 270. >> Substitution pattern not terminated at test.pl line 276. >> >> >> _______________________________________________________________ >> >> Don't miss the 2002 Sprint PCS Application Developer's Conference >> August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm >> >> _______________________________________________ >> Expectperl-discuss mailing list >> Exp...@li... >> https://lists.sourceforge.net/lists/listinfo/expectperl-discuss >> > > _______________________________________________________________ > > Don't miss the 2002 Sprint PCS Application Developer's Conference > August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm > > _______________________________________________ > Expectperl-discuss mailing list > Exp...@li... > https://lists.sourceforge.net/lists/listinfo/expectperl-discuss |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X