Re^4: run TreeTagger in Windows

Replies are listed 'Best First'.
Re^5: run TreeTagger in Windows by BrowserUk (Patriarch) on Mar 03, 2009 at 15:35 UTC
From my reading of the OPs situation, the other end of the fifo is a pre-existing application. And if that application is using fifos, it must run on unix. Probably on a unix server? Short of porting that to Windows, I don't see how the two are going to communicate? Even cygwin doesn't provide a mkfifo emulation, and I've never heard of anyone successfully connecting to a unix fifo using a Windows Named Pipe. I guess it might be possible via something like Samba? Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. "Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."	[reply]
Re^6: run TreeTagger in Windows by ikegami (Patriarch) on Mar 03, 2009 at 17:13 UTC
From my reading of the OPs situation, the other end of the fifo is a pre-existing application. That's my assumption as well. I don't see how the two are going to communicate? Through the fifo created using `CreateNamedPipe` as opposed to the fifo created using `mkfifo`. The name of the fifo used by the pre-existing application should be configurable, assuming the pre-existing application is aware of fifos in the first place. The module could be interfacing with a tool that doesn't accept input via STDIN or doesn't produce output on STDOUT. it might be possible via something like Samba? do you think the pre-existing application is running on a separate machine? Do unix fifos work over NFS?	[reply] [d/l] [select]
Re^7: run TreeTagger in Windows by BrowserUk (Patriarch) on Mar 03, 2009 at 17:56 UTC
Looking around I see that there is a Windows executable version of TreeTagger available, but there is no way that Alvis::TreeTagger is ever going to work on Windows. The name of the fifo used by the pre-existing application should be configurable, It doesn't use fifos, just plain files. Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. "Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."	[reply]
Re^5: run TreeTagger in Windows by lilli (Initiate) on Mar 03, 2009 at 15:25 UTC
Changing what child? Could you maybe be more specific on how a solution could be obtained? Bests, -lilli.	[reply]
Re^6: run TreeTagger in Windows by ikegami (Patriarch) on Mar 03, 2009 at 15:30 UTC
Isn't the point of the creating the pipes so their names can be passed to a child process? If so, create the named pipes using the Windows system call (`CreateNamedPipe`) instead of `mkfifo` and pass the name of those pipes to the child process.	[reply] [d/l] [select]
Re^7: run TreeTagger in Windows by BrowserUk (Patriarch) on Mar 03, 2009 at 15:38 UTC
Isn't the point of the creating the pipes so their names can be passed to a child process? That's what anonymous pipes are used for. Named pipes allow one process to create a named entity that any other unrelated process can find and connect to by going through the file system. Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. "Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."	[reply]