lement, requires almost everywhere.
Well, if we are very far, it will be just little step to be closer. On
other case we will be very far forever. If you mean hypotetical one-step
transition mega-patch in future, it will breaks too many things at once to
be something real.
--
Andrey A. Chernov
On Mon, Feb 25, 2002 at 17:23:53 +0300, Andrey A. Chernov wrote:
> Your initial fix was incorrect, but intention was right. should
> declare gid_t by itself. Sample quotes included below.
>
> >From IEEE P1003.1 Draft 7:
>
> NAME
> 8332 grp.h.group structure
> 8
On Mon, Feb 25, 2002 at 16:33:07 +0200, Sheldon Hearn wrote:
>
> However, the standard expects gid_t to be defined in , so if
> you just need gid_t, and not prototypes for getgr*(), then that's the
> one to include.
POSIX reguire gid_t to be specified not only in but in
t
ME
16663 getgrgid, getgrgid_r.get group database entry for a group ID
16664 SYNOPSIS
16665 #include
1 struct group *getgrgid(gid_t gid);
16667 TSF int getgrgid_r(gid_t gid, struct group * grp, char * buffer,
16668 size_t bufsize, struct group ** result);
--
Andrey A. Chernov
http://ache.pp.ru
SI_SOURCE or _POSIX_SOURCE to get standard conformance.
All those functions clearly marked as Nonstandard extensions in
corresponding string.h section.
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
em headers instead.
> > 3) Programs which not follows rule #2 must be fixed by removing
> > prototypes in question from their headers.
>
> What about the ANSI standard regarding polluting the user's
> name space?
Use standard way - #define _ANSI_SOURCE to switch th
tation is not related to Linux that way.
2) Program must not prototype by itself system-wide functions and should
relay on system headers instead.
3) Programs which not follows rule #2 must be fixed by removing
prototypes in question from their headers.
--
Andrey A. Chernov
http://ache.p
Can anybody recommend some incoming mail virus scanner soft smoothly
integrated with sendmail or procmail, keep its virus database fresh and
eaten small amount of resources (not perl, please)?
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
On Thu, Jun 08, 2000 at 03:07:48AM +0900, Daniel C. Sobral wrote:
> "Andrey A. Chernov" wrote:
> >
> > 3) "op" restore default color pair, not normal one (it involves syscons and
> > termcap fixing and manpage improvements)
>
> Is that why w3m an
On Mon, Jun 05, 2000 at 08:42:47AM +0900, Daniel C. Sobral wrote:
> Huh? I'm obviously missing something here... Why would the branches be
> damaged by this?
Because they forked. It cause merge troubles on the next import into the
vendor branch forever.
--
Andrey A. Chernov
<[E
urn off tracing */
--
Andrey A. Chernov
<[EMAIL PROTECTED]>
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
the past first, which ought to be a standard practice for
> committers.
There is no more standard practice left since CVS branches rulez.
--
Andrey A. Chernov
<[EMAIL PROTECTED]>
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
On Sat, Jun 03, 2000 at 07:10:56PM +0200, Gerald Pfeifer wrote:
> On Fri, 26 May 2000, Andrey A. Chernov wrote:
> > Yes, #define was a quick solution.
> > We need either to add a stub or to import ncurses author fix (removing
> > all trace function from production library
ce function from production library).
Latest is better IMHO, but I left to choose best way to Peter.
--
Andrey A. Chernov
<[EMAIL PROTECTED]>
http://nagual.pp.ru/~ache/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
14 matches
Mail list logo
