AOLserver's documentation woes and its future

On 9/5/06, Titi Ala'ilima <tigreoho.com> wrote:
> Rick Gutleber wrote:
> > > 2) The biggest bang for our buck would be
improving the Tcl language
> > > and the codebase available for it rather than
bringing in another popular language.  It took Rails to put
Ruby on the map.  What would our Rails be?
> > >
> > I would be careful to say "improve upon, or
enchance the Tcl libraries"
> > rather than the language.
>
> I mean improving the language as well.  As Dossy said,
there are a few things that could be added to the language
that would "make the language geeks go
'ooh!'", and a few others that would just make life
a little more powerful.  This is the sort of stuff that most
of us can't take as active a role in doing, but they would
still make a big difference.

Don't forget to look at XoTcl which runs just fine in
AOLserver.

http://media.wu-wien.ac.a
t/

>

-- 
Dave Bauer
davesolutiongrove.com
http://www.solutiongrove
.com


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to
<listservlistserv.aol.com> with the
body of "SIGNOFF AOLSERVER" in the email
message. You can leave the Subject: field of your email
blank.

FYI:

I did some more work on getting nsproxy to work under
windows.  The next 
problem we run into is that it makes use of readv() and
writev() which 
are not directly available in windows.  Some research that I
did 
indicates that some compilers have sort of
"wrappers" for them but even 
those may not work out of the box.  Personally I am not a
windows 
programmer so "porting" that is out of my
league.

To summarize: the sticking points here are poll(), readv()
and writev(), 
all of which have analogues on windows, but there would need
to be 
something of a rewrite to make it more OS-independent.

Rusty


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to
<listservlistserv.aol.com> with the
body of "SIGNOFF AOLSERVER" in the email
message. You can leave the Subject: field of your email
blank.