Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
comp.lang.tcl
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Message from discussion Separating stderr and stdout with exec/fileevent
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Mumit Khan  
View profile  
 More options Feb 2 1999, 3:00 am
Newsgroups: comp.lang.tcl
From: k...@xraylith.wisc.edu (Mumit Khan)
Date: 1999/02/02
Subject: Re: Separating stderr and stdout with exec/fileevent
Print | View thread | Show original | Report this message | Find messages by this author
In article <36B6C77E.7...@cnet.francetelecom.fr>,
Alexandre Ferrieux  <alexandre.ferri...@cnet.francetelecom.fr> wrote:

>Okay. So it looks like for an *official* Cygwin-based Win32 port of Tcl
>to exist, some kind of deal should be made between Cygnus and Scriptics.
>Any hope ?

It's upto the customer/user, not up to Scriptics. Tcl/Tk is already free
and part of Cygwin distrib. However, the applications you ship that is
linked against the free/GPL'd cygwin becomes GPL'd unless you buy a
commercial version from Cygnus.

btw, I may have misspoken about fileevent issue -- I've never tried
fileevent on a changing file, but rather use on a pipe when I exec
apps. I don't know if that doesn't work with the stock version.  My
usage is so simple that it may just not be affected by the deeper
problem with the Tcl windows port.

>Side-note for people outside Cygnus: what about David Korn's U/Win ?
>Technical issues ? Legal ?

UWIN is a commercial product and not redistributable. I have patches
for it somewhere, and I believe I have 8.0p2 binaries available on my
site.

All the non-native win32 ports have the same issue -- you'll need to
do some modifications to the windows side to make sure pathnames and
filesystem mounts are translated correctly, process environment and
current directory is kept in sync with the runtime, etc.

You had mentioned Interix at one point (I have patches for that too),
and that's a competely different beast, besides the fact that it's a
NT-only product. It's Unix for all purposes, so you'll be using the
X interface.

Regards,
Mumit


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google