Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

200
Views
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 answers
Answer question

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 Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!