Page MenuHomeFreeBSD

Use C99 types in MSDOSFS system code in anticipation of makefs msdos support
ClosedPublic

Authored by smahadevan_freebsdfoundation.org on May 19 2017, 3:51 PM.
Tags
None
Referenced Files
Unknown Object (File)
Mar 2 2024, 4:36 PM
Unknown Object (File)
Feb 19 2024, 10:05 PM
Unknown Object (File)
Jan 6 2024, 5:08 AM
Unknown Object (File)
Dec 20 2023, 3:18 AM
Unknown Object (File)
Dec 10 2023, 10:04 PM
Unknown Object (File)
Sep 20 2023, 4:43 PM
Unknown Object (File)
Sep 6 2023, 9:58 AM
Unknown Object (File)
Aug 16 2023, 12:15 PM
Subscribers

Details

Summary

General types cleanup in msdosfs code only. This also helps reduce diffs with NetBSD msdosfs libraries and msdos support in makefs.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

sys/fs/msdosfs/denode.h
106–107 ↗(On Diff #28570)

I noticed NetBSD still has u_long here (and elsewhere in this file)

sys/fs/msdosfs/denode.h
106–107 ↗(On Diff #28570)

Do we want to prioritize the diff reduction or consistency with the rest of our code and style(9) ("The project is slowly moving to use the ISO/IEC 9899:1999 (``ISO C99'') unsigned integer identifiers of the form uintXX_t...")? It seems they are sometimes using uXXX_t and other times using u_XXX_t.

sys/fs/msdosfs/denode.h
106–107 ↗(On Diff #28570)

We definitely want to use C99 fixed width types where the exist -- so we'll prefer int32_t to u_int32_t always.

This doesn't apply to the other convenience typedefs though -- u_long vs unsigned long. Does NetBSD's makefs msdos support include the appropriate header(s) to define u_long already?

sys/fs/msdosfs/denode.h
106–107 ↗(On Diff #28570)

Ah my mistake, this is simply a convenience typedef, NetBSD has the same typedefs set up in sys/types.h. I will revert these changes for the u_long and u_char typedefs.

  • Removed whitespace and style changes on lines other than the ones affected in this diff
  • Kept u_long, u_char, etc. as is
This revision is now accepted and ready to land.May 19 2017, 5:39 PM
This revision was automatically updated to reflect the committed changes.