Purpose: discuss what POSIX functionality is missing from Tcl.
Tcl is often promoted as a cross-operating system programming language. POSIX is the Portable Operating System Interface (what's the X?). FW: I think it's just that there's a tradition of naming OSes "*ix"
Cla The name is of course derived from UNIX.
The POSIX functions are supported, to various degrees, across many different platforms. How does Tcl's default functionality map to the POSIX description of a portable Operating System?
In theory, one should be able to get to most aspects of POSIX from the Tcl language without resorting to writing one's own extension. At worst case, there should be easy access to one or more extensions that provide access to all of the POSIX standard functionality.
POSIX defines things such as:
Some missing things:
DKF: Commentary on the above list of missing things:
What I'd like:
CL agrees with Donal, sometimes enthusiastically, while continuing to pine for Thread functionality to share procs (or equivalent).
Strick: Are any of these Posix calls missing from TclX? (And thanks for not getting us messed up in Threads!)
FW: Out of curiosity, how many of these does Java fulfil?
DKF: I don't remember for sure, but they've definitely got an mmap() equivalent.
Sarnold 11/01/2005 Wouldn't you like to have some socket options like with setsockopt() function?
DKF: They'd be nice as a small TIP, but they're not so much a part of any posix support as they'd be portable to other platforms (*ahem*Windows*ahem*) too.
RFox: Which of the POSIX Standards are we talking about? There's .1 which are core OS Services, there .1b which are real-time services I, that's where shared memory and (IIRC) mmap lives .1c is where pthreads lives. .2 we're probably not interested in. As that's the command shell and common utilities.