public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@ecoscentric.com To: unassigned@bugs.ecos.sourceware.org Subject: [Bug 1002110] vfscanf does not support "hh" conversion Date: Tue, 08 Dec 2015 20:44:00 -0000 [thread overview] Message-ID: <bug-1002110-777-pJky0tEPf0@http.bugs.ecos.sourceware.org/> (raw) In-Reply-To: <bug-1002110-777@http.bugs.ecos.sourceware.org/> Please do not reply to this email, use the link below. http://bugs.ecos.sourceware.org/show_bug.cgi?id=1002110 Jonathan Larmour <jifl@ecoscentric.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|high |low Status|UNCONFIRMED |RESOLVED CC| |jifl@ecoscentric.com Resolution|--- |WONTFIX Severity|critical |enhancement --- Comment #1 from Jonathan Larmour <jifl@ecoscentric.com> --- The eCos C library was written to the ISO C 90 standard. The 'hh' size specifier was added in the C99 standard. We do not have C99 support in this and many other ways. So indeed %hhx would fail. Adding 'hh' support, along with other C99 additions would be quite an enhancement, and is considered a low priority at this time. I suggest you use %c with the first element of a two char string (so you can have a NULL terminator) followed by a call to strtoul() with base 16. I'm marking this WONTFIX for now, although I'd have no problem with a tested patch if one appeared. Jifl -- You are receiving this mail because: You are the assignee for the bug.
next prev parent reply other threads:[~2015-12-08 20:44 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-12-04 1:41 [Bug 1002110] New: " bugzilla-daemon 2015-12-04 1:44 ` [Bug 1002110] " bugzilla-daemon 2015-12-08 20:44 ` bugzilla-daemon [this message] 2015-12-04 1:41 [Bug 1002110] New: " bugzilla-daemon 2015-12-04 1:44 ` [Bug 1002110] " bugzilla-daemon 2015-12-08 20:44 ` bugzilla-daemon
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-1002110-777-pJky0tEPf0@http.bugs.ecos.sourceware.org/ \ --to=bugzilla-daemon@ecoscentric.com \ --cc=unassigned@bugs.ecos.sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).