> On 13 Jul 98 at 11:27, Alexander Yuryevich Zvyagin wrote:
>
>
> > I've changed your macro (see below).
> >
> >
.... deleted ....
>
> I'd like to mention we are speaking not about but some bugs but
> about known features of CINT.
>
> Since CINT knows how the object was created it may treat either
> "character" (I mean "." or "->") the proper way according the real
> definition of the object /pointer (By the way it would be better all
> C++ compiler make users free of this headache too).
>
> I'd like to mention that there is difference between CINT language
> and C++ (scope rules, object / pointers id's etc) otherwise
> C++ is useless as an "interactive" script language.
>
> See: http://root.cern.ch/root/CintInterpreter.html
> "ROOT/CINT Extensions to C++"
>
Is there a description of the scope rules for Cint? The html you refer to
is not very appropriate; it does not address the scope rules directly.
Basically, I avoid scope problems by structuring my macros appropriately.
This sometimes creates problems when trying to write modular pieces of
macros. It would be nice to have an explanation of the scope rules of Cint,
so one can proceed with a clear understanding of how it actually works.
Ken