6 Apr
2012
6 Apr
'12
12:48 a.m.
On Thu, 5 Apr 2012 17:31:59 -0700 (PDT)
Darrell Anderson <humanreadable(a)yahoo.com> wrote:
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.
It depends - presumably it should make a difference
since it simply adds the
fat-fingers : 'should not' make a difference...
Otherwise we need preprocessor conditions in the patch when to merge
the changes.
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