Re: [ROOT] conflict in interpreting ls(Option_t)

From: Rene Brun (Rene.Brun@cern.ch)
Date: Thu Apr 19 2001 - 09:27:29 MEST


Hi Robert,

You are right. I did not realize the side effect of my mods to TCollection::ls
in functions like TGeometry::ls, TNode::ls.
I have modified TCollection::ls in CVS to use the wildcarding option
only when a "*" is part of the option.

Thanks for reporting this problem.

Rene Brun

Robert Hatcher wrote:
> 
> There appears to be a conflict in how various components use the Option_t
> arg of the "ls" method.  In particular TGeometry picks out individual
> characters in deciding what parts to display (r=rotations, s=shapes,
> n=nodes).  Each of these components is a list, which it call ls() on.
> But then it passes on the input Option_t arg to this call.  Alas:
> 
> cvs log TCollection: (from whence TList gets it's ls() method)
>  | revision 1.12
>  | date: 2000/12/26 14:17:57;  author: brun;  state: Exp;  lines: +44 -5
>  | Support for wildcarding in functions Draw, ls and Print.
> 
> means that TCollection attempts to use that arg for matching components.
> This means that TGeometry.ls("rsn2") fails to give anything meaningful
> because no rotations, shapes or nodes are named "rsn2".
> 
> -robert
> 
> Robert W. Hatcher   |  rhatcher@slac.stanford.edu
> Research Associate  |  650.926.3171  [FAX 4001 or 3587]
> Stanford University |  PO Box 4349, MS #63, Stanford CA 94309



This archive was generated by hypermail 2b29 : Tue Jan 01 2002 - 17:50:43 MET