hmm...yes, I thought so too, what I always found on the net was that in windows it always just kills the process, you can't really send any other signals between processes.
The beauty about signals is that they behave like interrupts, I can send a signal to a process, and it will automatically handle it using a signal handler, I don't have to do any polling which can become quite troublesome. Well then, as there is no way to use signals on windows, except if I use cygwin, what would be the best way to go about it then, maybe named pipes? I'm not really an expert in programming, only basic knowledge, so I'm kind of stumbling forward (^_^) and any help is really appreciated...not to mention that linux/unix just seems easier than windows in terms of programming. Yuck, although the code for a simple named pipe server/client looks really awful, too troublesome, might just go with environment variables instead, although then I again have to deal with constant polling...T_T [EMAIL PROTECTED] wrote: > I don't think so. When Perl was ported, it was made so that its kill > function (which does the same thing) simply forces the process with > pid to exit(sig). > > Cygwin Perl might be different, so who knows. > > On 5/16/07, Kenneth Forsb�ck <[EMAIL PROTECTED]> wrote: >> Hi, >> >> I know this is not the right place to ask, but after tediously searching >> the net I simply haven't found any answers, and the tcc mailing list is >> the only place left I can think of where I could possibly find an answer. >> >> Is there a windows equivalent or is it somehow possible to >> emulate/translate/something else, the c function kill(pid, sig)? I know >> the function is highly available on other systems, but for some reason >> windows only has raise, which doesn't help me, as I want to send a >> signal to an other process. >> >> Multithreading is too troublesome, so are pipes, sockets, etc., I'd >> simply want to use signals, the only problem being it's not available in >> windows, thus not really cross-platform...so I'd need an alternative for >> the windows version of my program. >> >> ~ Kenneth >> >> >> _______________________________________________ >> Tinycc-devel mailing list >> [email protected] >> http://lists.nongnu.org/mailman/listinfo/tinycc-devel >> > > > _______________________________________________ > Tinycc-devel mailing list > [email protected] > http://lists.nongnu.org/mailman/listinfo/tinycc-devel > _______________________________________________ Tinycc-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/tinycc-devel
