Empresas
Empleos
  • Sobre nosotros
  • Soluciones
    • Publicación de vacantes
      Publica tu vacante y recibe candidatos calificados en 48h.
    • Evaluación de candidatos
      500+ pruebas técnicas y psicológicas, más anti-fraude.
    • Headhunting
      Búsqueda ejecutiva a la medida de principio a fin.
    • Nómina + EOR
      Dispersión de nómina y EOR en más de 15 países de LATAM.
  • Precios
  • Empleos

0

203
Vistas
Why BSON is not using uint32_t instead of int32_t for document lenght

According to BSON specification an int32_t is used for the total number of bytes comprising the document.

I can also see that mongo-c-driver is using Libbson and it's using int32_t.

But what is the reason to use signed integer instead of unsigned integer?

the document size will never be below 0. Can someone please explain the reason?

over 4 years ago · Santiago Trujillo
1 Respuestas
Responde la pregunta

0

Document size is limited to 16 MB, which fits in a signed 32-bit integer with room to spare.

While document size limits larger than 16 MB were considered, my guess is there was no serious consideration of document sizes exceeding 2 GB, therefore the difference in range afforded by using unsigned 32-bit integers for length wasn't a meaningful benefit.

Thus, there is no reason to use an unsigned type.

Reasons to NOT use an unsigned type:

  • Wraparound potential from UINT_MAX to 0.
  • -1 could be used as a special designator.
over 4 years ago · Santiago Trujillo Denunciar
Responde la pregunta
Encuentra empleos remotos

¡Descubre la nueva forma de encontrar empleo!

Top de empleos
Top categorías de empleo
Empresas
Publicar vacante Precios Comercial
Legal
Términos y condiciones Política de privacidad
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Recomiéndame algunas ofertas
Necesito ayuda