6 Apr
2012
6 Apr
'12
2:31 a.m.
On Thu, 5 Apr 2012 18:27:04 -0700 (PDT)
Darrell Anderson <humanreadable(a)yahoo.com> wrote:
It mostly implements
bounds-checking on top of C++ STL vectors.
g++ actually already knew what to do with the source code (since it was
suggested in the error messages David posted), it just didn't fix it
automatically since the former code is not valid C++98.
I can test here (gcc 4.4.4). If there are no build
failures I still need a way to test functionality before pushing the
patch to GIT. How would that section of code be tested after
installation? There is zero semantic change, it is only a
matter of anal
C++ standards compliance.
I just finished building tdebase with the patch on Slackware 13.1
(gcc 4.4.4). No build failures.
How do I test functionality. What does easyvector do?
I'll push to GIT if somebody provides a "signoff" approval.
Darrell
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-devel-unsubscribe(a)lists.pearsoncomputing.net For additional
commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net Read
list messages on the web archive:
http://trinity-devel.pearsoncomputing.net/ Please remember not to
top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting