Date: Tue, 16 Mar 2021 17:11:07 +0700 From: Eugene Grosbein <eugen@grosbein.net> To: =?UTF-8?Q?Ionu=c8=9b_Mihalache?= <ionut.mihalache1506@gmail.com>, freebsd-hackers@freebsd.org Subject: Re: UCL library bug Message-ID: <2b96997e-40fb-f337-d94b-60c4f1a2f31e@grosbein.net> In-Reply-To: <CAOxbktb3cQWHUgBD1yB==pMg8p2JkDAPx0-HQ6RZvQ-v0LRY1Q@mail.gmail.com> References: <CAOxbktb3cQWHUgBD1yB==pMg8p2JkDAPx0-HQ6RZvQ-v0LRY1Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
16.03.2021 16:03, Ionuț Mihalache wrote: > Hello, > > I am using the ucl library to write in a file 64bit values. The data type > is uint64_t or int64_t; on write I use %lu or %ld regarding the type and > everything works, on read on the other hand something weird seems to happen: > > I read using %ld only and for small value it works, for values like > 18,374,686,479,671,672,848 > the ucl type type is recognized as UCL_STRING instead of UCL_INT and I > don't know why this is happening. Is there a bug in the library? Does it help if you use %lld instead? Or maybe %jd ?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2b96997e-40fb-f337-d94b-60c4f1a2f31e>