[Jmol-users] Re: Wildcard behavior

[Miguel H. <mt...@mt...>]

>>>>But even
>>>> select [C]3:A.O5*
>>>>is not working at the moment
>>>>http://www.imb-jena.de/cgi-bin/SCOPlnk.exe?JMOL=264d
>>>>in current RasMol
>>>> select [C]3:A.O5*
>>>> select C3:A.O5*
>>>> select C3A.O5*
>>>>all select the same expected atom.

I just checked in code to correct this.

All of the above successfully select the same atom.

It also works with insertion codes ... if there happened to be a 3^A
insertion code in the file then the following would work:
  select c3^a
  select c3^aa.05*


Miguel



Note for programming language techies
=====================================
The RasMol expression evaluation behavior is ambiguous and is dependent
upon what was defined at the time that the expression is evaluated.

Consider the following:

  define c3a <some selection>

  select c3a

The behavior of the select c3a changes depending upon whether there was a
variable called c3a already defined. That definition may have been in
another script file that ran the current script file as a 'subroutine'.
Therefore, interpretation of the string 'c3a' must be delayed until
runtime.

I am not happy about this. And I am not happy that I had to hack the Jmol
compiler/interpreter to make this work. But what's done is done :-(