Re: man 3 getopt char * const argv[] - is const wrong ?

2011-02-13 Thread Julian H. Stacey
Matthias Andree wrote: > Am 13.02.2011 18:15, schrieb Julian H. Stacey: > > Hi, > > Thanks to all respondents, I'll re-read comments in a bit, > > I went searching for reference: > > > > Matthias wrote: > >> the prototype is in line with the Single Unix Specification v4 aka IEEE > >> Std. 1003.1-20

Re: man 3 getopt char * const argv[] - is const wrong ?

2011-02-13 Thread Julian H. Stacey
> Not quite what you asked for but this may help in making > sense of const > > $ cdecl # from /usr/ports/devel/cdecl Thanks Bakul, nice ! Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Mail plain text; Not quo

Re: man 3 getopt char * const argv[] - is const wrong ?

2011-02-13 Thread Bruce Cran
On Sunday 13 February 2011 17:15:37 Julian H. Stacey wrote: > Hi, > Thanks to all respondents, I'll re-read comments in a bit, > I went searching for reference: > > Matthias wrote: > > the prototype is in line with the Single Unix Specification v4 aka IEEE > > Std. 1003.1-2008 (sorry no URL, I hav

Re: man 3 getopt char * const argv[] - is const wrong ?

2011-02-13 Thread Bakul Shah
On Sun, 13 Feb 2011 13:20:58 +0100 "Julian H. Stacey" wrote: > Hi Hackers > Ref.: man 3 getopt > int getopt(int argc, char * const argv[], const char *optstring); > > Ref.: K&R 2nd Ed P.211 last indent, 2nd sentence > The purpose of const is to announce objjects that may be > p

Re: man 3 getopt char * const argv[] - is const wrong ?

2011-02-13 Thread Matthias Andree
Am 13.02.2011 18:15, schrieb Julian H. Stacey: > Hi, > Thanks to all respondents, I'll re-read comments in a bit, > I went searching for reference: > > Matthias wrote: >> the prototype is in line with the Single Unix Specification v4 aka IEEE >> Std. 1003.1-2008 (sorry no URL, I have checked my loc

Re: man 3 getopt char * const argv[] - is const wrong ?

2011-02-13 Thread Julian H. Stacey
Hi, Thanks to all respondents, I'll re-read comments in a bit, I went searching for reference: Matthias wrote: > the prototype is in line with the Single Unix Specification v4 aka IEEE > Std. 1003.1-2008 (sorry no URL, I have checked my local copy, check > you can acces

Re: man 3 getopt char * const argv[] - is const wrong ?

2011-02-13 Thread Jilles Tjoelker
On Sun, Feb 13, 2011 at 01:59:38PM +0100, Matthias Andree wrote: > Am So, 13.02.2011, 13:20 schrieb Julian H. Stacey: > > Hi Hackers > > Ref.: man 3 getopt > > int getopt(int argc, char * const argv[], const char *optstring); > > Ref.: K&R 2nd Ed P.211 last indent, 2nd sentence > > The purp

Re: man 3 getopt char * const argv[] - is const wrong ?

2011-02-13 Thread Matthias Andree
Am So, 13.02.2011, 13:20 schrieb Julian H. Stacey: > Hi Hackers > Ref.: man 3 getopt > int getopt(int argc, char * const argv[], const char *optstring); > Ref.: K&R 2nd Ed P.211 last indent, 2nd sentence > The purpose of const is to announce [objects] that may be > placed in read-

man 3 getopt char * const argv[] - is const wrong ?

2011-02-13 Thread Julian H. Stacey
Hi Hackers Ref.: man 3 getopt int getopt(int argc, char * const argv[], const char *optstring); Ref.: K&R 2nd Ed P.211 last indent, 2nd sentence The purpose of const is to announce objjects that may be placed in read-only memory, and perhaps to increas opportunities

Re: SO_SETFIB socket option

2011-02-13 Thread Naveen Gujje
On Sun, Feb 13, 2011 at 2:20 AM, Julian Elischer wrote: > On 2/12/11 8:40 AM, Daniel Eischen wrote: > >> On Sat, 12 Feb 2011, Naveen Gujje wrote: >> >> Hi All, >>> >>> On my FreeBSD 7.2 box, I've two routing tables (FIBs). Fib 0 and Fib 1 >>> (net.fibs = 2). >>> >>> I have a simple echo client w