Hi Valery, not always, depending on a number of connections and logic. I practically experinced a case where changing from TList to THashList in a similar situation reduced loading time from minutes to fraction of a second. Rene experienced it too with TROOT::fListOfxxx. Once you create all the list objects "on fly" in TQObject it is not very important that THashList is heavier than TList. So why don't you just change it to THashList in the header? :) look-up time: assume all connections have the same priority (typical case btw). CINT: it is always better to be the best in your business, i.e. saying that "someone is slower anyway - why should I care?" is not a very good reason :) Cheers, Anton Valeriy Onuchin <Valeri.Onoutchine@cern.ch>@mail.cern.ch on 03/08/2002 04:29:34 PM Please respond to Valeri.Onoutchine@cern.ch Sent by: onuchin@mail.cern.ch To: anton.fokin@nl.fortisbank.com cc: roottalk@pcroot.cern.ch Subject: Re: [ROOT] ROOT signal/slot question Hi Anton, in my opinion, "look-up time" is always much smaller than invocation of "CINT method". You can control "look-up time" with http://root.cern.ch/root/htmldoc/TQObject.html#TQObject:HighPriority Regards. Valeriy anton.fokin@nl.fortisbank.com wrote: > Hi guys, > > what's the reason to not use THashList instead of TList in TQObject, etc? > Wouldn't it speed up signal->slot search? > > Cheers, > Anton > [INFO] -- Virus Manager: Message contains no viruses. ___________________________________________________________________________ This e-mail is sent for the sole attention of the identified addressee and its contents are provided for information purposes only. Fortis Bank makes no warranty or representation as to the accuracy and completeness of any information and does not assume whatever commitment hereby. Legally binding obligation can only arise for, or be entered into on behalf of, Fortis Bank by means of a written instrument, signed by two duly authorised representatives of Fortis Bank. Fortis Bank excludes any liability whatsoever for any direct or consequential loss arising from the use, or reliance on, this e-mail or its contents. ___________________________________________________________________________
This archive was generated by hypermail 2b29 : Sat Jan 04 2003 - 23:50:45 MET