|
|
Blitz Support : |
From: Julian Cummings (cummings_at_[hidden])
Date: 2004-01-20 15:58:54
Hi Dave,
Dave Johnson wrote:
> Julian,
>
> I commented out lines 100-105 in vector.h and the copy constructor
> warnings went away,
Good.
> but it still gives the rest of the warnings as follows:
>
> C:\Blitz\blitz\memblock.h(80) : warning C4267: 'argument' : conversion
> from 'size_t' to 'int', possible loss of data
This is coming from the member function allocate(). We need to change
the argument type here from int to size_t for consistency. If you do
this in both the function declaration and in the definition in
<blitz/memblock.cc>, the compiler warning should go away. I have taken
the liberty of commiting these changes to the cvs repository already,
along with the change to <blitz/vector.h>.
>
> I see the following reports in the lists with no followups. I don't
> understand how I would know if these were fixed or not. And which
> changes were important for them.
>
> * To: blitz-bugs_at_[hidden]
> * Subject: [Blitz-bugs] Bug with range-assignments in
> Fortran-style arrays, if optimizing
> * From: Christopher Eltschka
> <christopher.eltschka_at_[hidden]>
> * Date: Thu, 07 Aug 2003 21:15:57 +0200
> * Organization: Physik
>
> * To: blitz-bugs_at_[hidden]
> * Subject: [Blitz-bugs] Ouch! (-O causes blitz 0.7 bug?)
> * From: Creon Levit <creon_at_[hidden]>
> * Date: Tue, 2 Dec 2003 19:29:39 -0800
>
OK, I hadn't noticed these bug reports, but I should probably take a
look then. I periodically take a peek and see what bug reports have
been made and answered. Fortunately, many times other users can and do
answer the questions. Otherwise, I will try to help or put the item on
a TODO list. But I only work on these things on a volunteer basis as my
time permits. I do the work because I am a user of blitz myself and
want to see its use continue. Support for blitz will continue to be of
a limited nature for the foreseeable future, unless I can find a way to
make this my full-time job and get paid for it! :-) I hope you
understand.
>
> I have liked the package so far in my usage. Much better than the
> other libraries out there. I'm just struggling to figure out how all
> the sources are kept current, and how to figure out where I need to
> look for fixes. Seems there a lot of source files that have changed
> since the big zip file was created. I haven't figured out if it is
> important to get any of the modified files or not.
It never hurts to do a "cvs update" and grab the latest repository
changes. The worst that can happen is that you run into a recent change
which causes some code of yours to break. When that happens, report it
and then use cvs to back off to a previous version of the offending
source code file in blitz. But please try not to report "bugs" which
have already been fixed in a more recent version of the blitz code.
Always check that your source is current first.
Thanks, Julian C.
-- Dr. Julian C. Cummings E-mail: cummings_at_[hidden] California Institute of Technology Phone: 626-395-2543 1200 E. California Blvd., Mail Code 158-79 Fax: 626-584-5917 Pasadena, CA 91125