public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ondra at iuuk dot mff.cuni.cz" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug stdio/15450] New: Refactor stdio-common/vfscanf.c Date: Thu, 09 May 2013 16:52:00 -0000 [thread overview] Message-ID: <bug-15450-131@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=15450 Bug #: 15450 Summary: Refactor stdio-common/vfscanf.c Product: glibc Version: unspecified Status: NEW Severity: enhancement Priority: P2 Component: stdio AssignedTo: unassigned@sourceware.org ReportedBy: ondra@iuuk.mff.cuni.cz Classification: Unclassified Hi, A code in vscanf is quite repetetive. I also found that copying arguments is often ineffectively done byte by byte. Could it be refactored in 2.19? -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2013-05-09 16:52 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-05-09 16:52 ondra at iuuk dot mff.cuni.cz [this message] 2014-06-13 18:06 ` [Bug stdio/15450] " fweimer at redhat dot com
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-15450-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@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).