[bug #19503] PostgreSQLChannel.m/newValueForDateTypeLengthAttribute milliseconds problem

[David Ayers]

Update of bug #19503 (project gnustep):

                  Status:                    None => Fixed                  
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #1:

Thanks... I the millisecond value was replacing the second value and wasn't
set itself.  Fixed in SVN.
I'm still a but surprised that the compiler doesn't optimize:
if (localuint > 2)
{ /*don't alter localuint */ }
if (localuint > 5)
{ /*don't alter localuint */ }
if (localuint > 9)
{ /*don't alter localuint */ }

to:
if (localuint > 2)
{ /*don't alter localuint */ 
  if (localuint > 5)
  { /*don't alter localuint */
    if (localuint > 9)
    { /*don't alter localuint */ }
  }
}

by itself but I'm not finding the time to investigate so changed it as you
suggested (but didn't update the indetation yet as I may still look into this
later.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?19503>

_______________________________________________
  Nachricht geschickt von/durch Savannah
  http://savannah.gnu.org/