On Tue, 2006-02-28 at 22:23 -0500, Sean Coates wrote:
> > The final decision will be of course up to you guys, but I would hope
> > that the patch be applied. The patch would make the page a little too
> > big, like you say, but I would vote for the consistency in page format
> > (I don't see cons
> The final decision will be of course up to you guys, but I would hope
> that the patch be applied. The patch would make the page a little too
> big, like you say, but I would vote for the consistency in page format
> (I don't see constants given as ranges elsewhere), than a slight page
> size in
Hi Nuno,
On Tue, 2006-02-28 at 22:54 +, Nuno Lopes wrote:
> Hi,
>
> I'm not sure we want to apply this patch. This will make the page too big
> and too verbose.
The final decision will be of course up to you guys, but I would hope
that the patch be applied. The patch would make the page a
Hi,
I'm not sure we want to apply this patch. This will make the page too big
and too verbose.
Why don't you crawl the PHP sources directly, instead of reading the docs,
which can be outdated and/or incorrect?
Nuno
- Original Message -
Hi there again,
Well, here is another modifi
TAKAGI Masahiro wrote:
> When you separate NCURSES_KEY_F*, it's better to unpluralize their
> descriptions.
Good point. Thanks for the correction. :-)
Kohei
--
Kohei Yoshida, Software Engineer
SlickEdit Inc. [ http://www.slickedit.com/ ]
Hi,
At Wed, 22 Feb 2006 15:40:27 -0500,
Kohei Yoshida wrote:
>
> Well, here is another modification I've made to the doc. In the ncurses
> category, some constants, such as NCURSES_KEY_F* and
> NCURSES_BUTTON*_RELEASED (and its cousins), are given as ranges. I've
> changed them to list individu
Hi there again,
Well, here is another modification I've made to the doc. In the ncurses
category, some constants, such as NCURSES_KEY_F* and
NCURSES_BUTTON*_RELEASED (and its cousins), are given as ranges. I've
changed them to list individual entries instead of the original ranges.
I needed to d
