Possible Color.h Bug

In color.h, two functions are defined for ColorI for endian color usage.

It appears both functions return the same value. Upon changing the functions to reflect what they are supposed to be returning, the resultant rendered image is miscolored.

inline U32 ColorI::getARGBPack() const
{
   return (U32(alpha) << 24) |
          (U32(red)   << 16) |
          (U32(green) <<  8) |
          (U32(blue)  <<  0);
}

...

inline U32 ColorI::getABGRPack() const
{
   return (U32(alpha) << 24) |
          (U32(red)   << 16) |
          (U32(green) <<  8) |
          (U32(blue)  <<  0);
}

This should be:

inline U32 ColorI::getARGBPack() const
{
   return (U32(alpha) << 24) |
          (U32(red)   << 16) |
          (U32(green) <<  8) |
          (U32(blue)  <<  0);
}

...

inline U32 ColorI::getABGRPack() const
{
   return (U32(alpha) << 24) |
          (U32(blue)   << 16) |
          (U32(green) <<  8) |
          (U32(red)  <<  0);
}

This assumes that the endian functions are as follows:

inline U32 ColorI::getRGBEndian() const
{
#if defined(TORQUE_OS_MAC)
    return(getRGBPack());
#else
    return(getBGRPack());
#endif
}

inline U32 ColorI::getARGBEndian() const
{
#if defined(TORQUE_OS_MAC)
   return(getABGRPack());
#else
   return(getARGBPack());
#endif
 }

Although logic shows that the second method of returning data is correct, the rendered image is clearly different than expected. Does this bug go deeper than color.h ? Or is the function naming convention simply not logically tied to the return value ?