From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-patches@cygwin.com
Subject: Re: /dev/clipboard pasting with small read() buffer
Date: Thu, 16 Aug 2012 16:23:00 -0000 [thread overview]
Message-ID: <20120816162245.GC14163@calimero.vinschen.de> (raw)
In-Reply-To: <502D10AF.1040501@redhat.com>
On Aug 16 09:24, Eric Blake wrote:
> On 08/16/2012 08:20 AM, Thomas Wolff wrote:
>
> >>> MB_CUR_MAX does not work because its value is 1 at this point
> >> So what about MB_LEN_MAX then? There's no problem using a multiplier,
> >> but a symbolic constant is always better than a numerical constant.
> > I've now used _MB_LEN_MAX from newlib.h, rather than MB_LEN_MAX from
> > limits.h (note the "_" distinction :) ),
> > because the latter, by its preceding comment, reserves the option to be
> > changed into a dynamic function in the future, which could then possibly
> > have the same problems as MB_CUR_MAX.
>
> POSIX requires MB_LEN_MAX to be a constant, only MB_CUR_MAX can be
> dynamic. We cannot change MB_LEN_MAX to be dynamic in the future.
...also, Cygwin's include/limits.h doesn't mention to convert to
a function.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
next prev parent reply other threads:[~2012-08-16 16:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 20:56 Thomas Wolff
2012-08-16 9:34 ` Corinna Vinschen
2012-08-16 12:12 ` Thomas Wolff
2012-08-16 12:31 ` Corinna Vinschen
2012-08-16 14:21 ` Thomas Wolff
2012-08-16 15:24 ` Eric Blake
2012-08-16 16:23 ` Corinna Vinschen [this message]
2012-08-17 8:44 ` Thomas Wolff
2012-08-17 9:23 ` Corinna Vinschen
2012-08-17 13:05 ` Thomas Wolff
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=20120816162245.GC14163@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-patches@cygwin.com \
/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: link
Be 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).