On Mon, Mar 28, 2022 at 09:03:07AM -0400, Mouse wrote:
> > If you want portable code, i'd refrain from using underspecified
> > types like `long' and just plain `int' in an interface!
>
> Depending on what you're trying to do, int or long int may well be the
> more portable choice. Using (for
> If you want portable code, i'd refrain from using underspecified
> types like `long' and just plain `int' in an interface!
Depending on what you're trying to do, int or long int may well be the
more portable choice. Using (for example) int32_t renders the code
nonportable to systems that don't
Hi,
On Wed, Mar 23, 2022 at 02:28:39PM +, Emmanuel Dreyfus wrote:
> I am almost certain I already raised that question, but I could not find
> where, and the issue remains to be fixed.
>
> NetBSD's src/lib/librefuse/fuse_opt.h
> struct fuse_opt {
> const char *templ;
>
Hello
I am almost certain I already raised that question, but I could not find
where, and the issue remains to be fixed.
NetBSD's src/lib/librefuse/fuse_opt.h
struct fuse_opt {
const char *templ;
int32_t offset;
int32_t value;
};
libfuse's
