tDOM nextSibling not working as expected.

Similar Threads:

1.tdom - not understanding "nextSibling"

I have a simple xml document:
<recordset>
 <division name="myname">
  <coe_division_name>MISSISSIPPI VALLEY</coe_division_name>
  <division_abbreviation>MVD</division_abbreviation>
 </division>
</recordset>

Whe I am parsing it and get to the node:
<coe_division_name>MISSISSIPPI VALLEY</coe_division_name>
I am running this code:
set myvar [$doc nextSibling]
however, the result is blank.

What would constitute a sibling?  How can I check if there is another
element on the same level of nesting right after the current element?

Thank you.

2.NASM does not have = and its %define does not work as I expected

NASM version 0.98.38 compiled on Sep 12 2003

I only want to make a linked strings like this, but it doesn't work as
I expeced

%define _link   0
xTable  db      'abc',0
        dw      _link
%define _link   $
        db      'd',0
        dw      _link
%define _link   $
        db      'efghijk',0
lnkhead dw      _link


     1                                  %define _link   0
     2
     3 00000000 61626300                xTable  db      'abc',0
     4 00000004 0000                            dw      _link  <=====
correct
     5                                  %define _link   $  <=== _link
is now = 6
     6 00000006 6400                            db      'd',0
     7 00000008 [0800]                          dw      _link <====
this should be 0006h but it's not !!
     8                                  %define _link   $ <=== _link
is now = A
     9 0000000A 65666768696A6B00                db      'efghijk',0
    10 00000012 [1200]                  lnkhead dw      _link <===
this should be 000Ah but it's not !!


    1

3.Range checking not working as expected?

4.trace does not work has expected

5.Expect not being able to work with a '$' within a variable

I have written an expect script which allows me to ssh to multiple
systems.  The expect script  is invoked through a bash script which
loops though all the systems.  The problem that I'm running into is
that the password of my systems have '$' within, so when I pass the
password to expect:

   ssh.exp system1 my$password myremotecommand

It returns with password incorrect.

I've tried escpaing the password by doing: my\$password and my\\\
$password - but when expect runs it:

set PASSWD  [lrange 1 1]

spawn ssh -p port user@system1
expect "password: "{
   sleep 1;
   send $PASSWD
}

Is it possible to escape the $ contained within the variable?

6. Expect not working with SSH on CygWin

7. expect command does not work on windows XP

8. List parsing not working as expected