Hi,
On Mon, 28 Oct 2002, zhangchi wrote:
> a block on a PC is what, a few killo?
I think 512K Adrian mentions is not what the C++ guys are referring to.
Perhaps they meant the filesystem block sizes which are usually limited
to 4K or 8K (although Linux only supports 4K on i686 machines, and 4K
is also the page size), not the fragment sizes, which are indeed (usually)
512K.
> I welcome any suggestion to go arround these limits
Instead of bypassing the limits, perhaps we should think about fishing
for such details of the code as subscript overflows. At least in the
Blast code this can be done by furnishing critical memory allocations
with exception catching. Every failure in new() can be made to throw
an exception which can be caught (and handled). Before accusing Draw()
(which, however, is not an unlikely candidate) one could check if our
side of the code performs as it should.
Simon
> On Sun, 27 Oct 2002, Adrian T Sindile wrote:
>
> > Hi, Vitaly!
> > Is it really the Draw() function, or is there some array dimension set by
> > the author of the macro? It is hard to think the Draw() function craps out
> > so easily... Just thinking loudly here.
> >
> > Adrian
> >
> > -------------------------------
> > Adrian Sindile
> > Research Assistant
> > Nuclear Physics Group
> > University of New Hampshire
> > phone: (603)862-1691
> > FAX: (603)862-2998
> > email: asindile@alberti.unh.edu
> > http://einstein.unh.edu/~adrian/
> >
> >
> >
>
-- Simon Sirca Dept of Physics, University of Ljubljana Tel: +386 1 4766-574 Jadranska 19 Fax: +386 1 2517-281 1000 Ljubljana, Slovenia
This archive was generated by hypermail 2.1.2 : Mon Feb 24 2014 - 14:07:28 EST