in reply to Re^3: problems using Expect.pm in foreach loop
in thread problems using Expect.pm in foreach loop

The postfix if (! $line=~m/^\s*exit\s*$/i) is not doing what you expected.

#!/usr/bin/env perl use strict; my $line = 'not an exit statment'; print "line matched ! =~\n" if (! $line =~ m/^\s*exit\s*$/i ); print "line matched !(=~)\n" if (! ($line =~ m/^\s*exit\s*$/i) ); print "line matched not =~ \n" if (not $line =~ m/^\s*exit\s*$/i ); print "line matched if !~\n" if ( $line !~ m/^\s*exit\s*$/i ); print "line matched unless =~\n" unless ($line =~ m/^\s*exit\s*$/i); __END__ line matched !(=~) line matched not =~ line matched if !~ line matched unless =~

The ! operator has a much higher precedence than the not operator does. Using parentheses with the ! applies it to the result of the match; not with its lower precedence does so by default.

When $exp->send sends the exit command to isql, isql disconnects and Expect.pm notices and handles that. If you are writing a production-quality program - especially one that will run automatically - you'll want to code your own checks for errors, disconnects, etc. OTOH, if this is for your own use only, run manually to simply automate a task, then you can usually get away with letting the Expect module handle anomalies. (I assume you're backing up whatever DB objects are being modified prior to letting a program make changes...)


Update: added != and unless tests as additional examples

Replies are listed 'Best First'.
Re^5: problems using Expect.pm in foreach loop
by gg48gg (Sexton) on Sep 22, 2011 at 04:11 UTC

    That was truly an excellent response keszler. Thank you for that! I understand now what was happening with my attempt to match "exit".

    Also, thank you for the added info about error checking the isql exit.

    Thanks everyone for your posts.
Re^5: problems using Expect.pm in foreach loop
by gg48gg (Sexton) on Oct 04, 2011 at 21:06 UTC
    just wanted to thank you for your exellent replies. Very helpful! THANK YOU!