[ksh93-integration-discuss] Re: [ast-users] /dev/tcp+/dev/udp notcompiled-in for Solaris ksh93r...

[Glenn Fowler]

On Tue, 12 Sep 2006 23:06:07 +0200 Roland Mainz wrote:
> "I. Szczesniak" wrote:
> > On 9/7/06, Roland Mainz <roland.mainz at nrubsig.org> wrote:
> > > Glenn Fowler wrote:
> > > > socket() not in libc
> > > > solaris is still in the 70's on this one
> > > > is it in -lsocket?
> > > [snip]
> > >
> > > Minor update (I just hit that problem again): It still doesn't work in
> > > ksh93r+_20060724... ;-(
> > 
> > Does ksh93 provide a property which can be used to check within a
> > script whether the shell has been built with networking capabilities?

> I would simply assume that ksh93 which is going to be shipped with
> Solaris Nevada always has networking capabilities. At least I am
> checking that on a regular basis...

> ... on the other side some kind of "capabilities" flags (for
> networking-, multibyte-, largefile- etc. support) in the output of the
> "getconf" builtin may be a nice idea...

we wouldn't put specifics for a single a.out in getconf just because
it happened to be a builtin for that a.out

I posted a /dev/tcp redirection tests for networking available

in general, though, properly iffe'd (configured) ast sw, ksh included,
with have networking, multibyte, largefile, enabled if the underlying
system supports it

that won't help script portability though ...