ROOT 2.22.10: Five buglet reports

From: Matthew D. Langston (langston@SLAC.stanford.edu)
Date: Mon Aug 16 1999 - 01:54:40 MEST 

Hello ROOT Team,

Here is a small list of five buglets that I was hoping you might
eventually fix for us:

1) The `root' command doesn't parse the "-I" flag correctly (or at least
   the way I expect it to work).  This works:

     $ root -I /foo/bar/baz

   but this doesn't:

     $ root -I/foo/bar/baz

2) The cint interpreter doesn't return an error code (i.e. it always
   succeeds), even if the interpreted script fails.  For example:

     $ cat foo.cxx 
     void
     foo()
     {
        exit( 1 );
     }
     $ root -b -l -n -q foo.cxx
     [snip]
     Processing foo.cxx...
     $ echo $?
     0

   Even if there are users who depend on this behavior, may I ask that
   an option be added to cint that enables the propagation of the error
   code.

   The absence of a meaningful return code makes it extremely difficult
   to write ROOT testsuites (I am currently having to parse the output
   with Expect).

3) The `root' command ignores the "-l" flag to disable the display of
   the ROOT splash screen.  No matter what I try, I can't suppress the
   ROOT splash screen.

4) ROOT's paths in a `.rootrc' file (e.g. Unix.*.Root.MacroPath) must be
   absolute - they can't be relative paths.  This makes it extremely
   difficult to write ROOT testsuites.

5) Static data members aren't initialized by the interpreter, even
   though the initialization is explicit in the implementation
   (e.g. .cxx) file.

Thanks!

--
Matthew D. Langston
SLD, Stanford Linear Accelerator Center
langston@SLAC.Stanford.EDU

This archive was generated by hypermail 2b29 : Tue Jan 04 2000 - 00:43:38 MET