No rotation clamping in Camera class?

I notice that the camera rotation (more specifically the mRot values) don't get clamped. If you start a mission and go into the fly cam mode (alt+c) while printing out the camera rotation values it just keeps going until it maxes/mins out the float. From what I understand it should be clamped as there is never a reason for it's value to go to those ranges and floating point precision issues will occur. Player objects, for example, clamp rotation between 0 and 6.28.

Noticed this when I was trying to compare camera rotation values in orbit mode. I added a clamp to mRot.z in the processTick for the Camera class and haven't noticed any issues.

Is there a reason the values are not clamped already?

Code I added was:

...
      pos += posVec;
   }

   // Clamp rotation value between 0 and M_2PI_F. ---
   while (mRot.z < 0.0f)
      mRot.z += M_2PI_F;
   while (mRot.z > M_2PI_F) 
      mRot.z -= M_2PI_F;
   // ---

   _setPosition(pos,mRot);

   // If on the client, calc delta for backstepping
   if (serverInterpolate || isClientObject())
   {
...