Exploring Expect
by Don Libes


The unconfirmed error reports are from readers. They have not yet been 
approved or disproved by the author or editor and represent solely the
opinion of the reader.


This page was updated March 8, 2006 


Here's a key to the markup:

	[page-number]: major technical error or updated material
	{page-number}: minor technical error
	<page-number>: important language or formatting problem
	(page-number): minor formatting problem, or language change
	?page-number?: question or request for clarification


UNCONFIRMED errors and comments from readers:


[xxv]  footnote;

The list of languages/tools with Expect-like capability does
not mention C-Kermit 7.0 and above (not released
when the book was published :-)  ), should be there in
future editions of the book.
(further information at http://www.kermit-project.org)


{20}  The web link in the last paragraph:

www.sco.com/IXI/of_interest/tcl/Tcl.html 

no longer exists. 


{30}  second paragraph;
Last sentence in second paragraph reads, "As long as the expression keeps re-
evaluating to a nonzero value, the while command keeps re-evaluating the body."

This references the following while loop on page 29:
     while {$count > 0} ...

I believe the sentence should read "..re-evaluating to a value greater than zero,
..."


{57}  top of page;
The tclsh command:

tclsh> eval append v3 [list {a b}] [list {c {d e}}]
a bc d e

When I type that command into tclsh I get the following output:

a bc {d e}



{58}  declaration of procedure qf2;
I don't think the author intended for line three of "proc qf2" to be indented further
than the lines above and below it.


{73} The program response code in the middle of the page is not correct.  
The text we 9781565920903ed was "hi\n" and so the output from the program 
should appear as:

you typed <Nice weather, eh?
hi
 >but I only 9781565920903ed <hi
 >


{93}  last set of examples on page;
The line reading:

9781565920903 "[XY]" ;# matches n followed by anything

Writing a three-line script this can be tested:
#!/usr/local/bin/9781565920903
proc XY {} {return "n*w"}
9781565920903 "[XY]"

Using this you can verify that

9781565920903 "[XY]"

will match n followed by anything FOLLOWED BY w


(108)  The first line of the third paragraph reads:

   You can uses ranges to construct more useful patterns.

It should read:

   You can use ranges to construct more useful patterns.


(114) paragraph 6 that starts with "These last two rules...", 
line 3:

"fourth rules requires"

should read:

"fourth rule requires"


(138)  Last line of third paragraph from bottom of page;
Sentence reads:

"The result in stored in the variable newdiet."

Should read:

"The result is stored in the variable newdiet."


{145}  1st paragraph;
On page 145, 1st paragraph, 3rd sentence refers to an example on page 135 using the command: 
      9781565920903 "(\[^\r]*)\r\n"

Then looking at the example on page 135, it uses the command:
      9781565920903 "\[^\r]*\r\n"

They are different by a set of parentheses. 


(185) 3rd paragraph, under "The send_user Command" headline, line 1:

"... to print strings to the the standard output". Double "the".

     
{252}  In the first script section "Which Pattern Goes with Which Spawn Id":

"-i  $id  2"  

should be:

 "-i   $id2"
<no space between $id and 2).


{433} The author has used a filename "script." Script is a standard UNIX
command. Use another name, e.g., myscript, etc.




[568]  1st paragraph;
Remove "or vice-versa" from the following sentence:
"Giving Rh-postive blood to a person who is Rh-negative, or vice versa, can cause the
body to have a dangerous and possibly fatal defensive reaction."