stdin

I'm writing a program where performance is quite important, but not critical. Currently I am reading in text from a FILE* line by line and I use fgets to obtain each line. After using some performance tools, I've found that 20% to 30% of the time my application is running, it is inside fgets . Are there faster ways to get a line of text? My application is single-threaded with no intentions to use multiple threads. Input could be from stdin or from a file. Thanks in advance. You don't say which platform you are on, but if it is UNIX-like, then you may want to try the read() system call, which

I'd like to download a web pages while supplying URLs from stdin. Essentially one process continuously produces URLs to stdout/file and I want to pipe them to wget or curl. (Think about it as simple web crawler if you want). This seems to work fine: tail 1.log | wget -i - -O - -q But when I use 'tail -f' and it doesn't work anymore (buffering or wget is waiting for EOF?): tail -f 1.log | wget -i - -O - -q Could anybody provide a solution using wget, curl or any other standard Unix tool? Ideally I don't won't want to restart wget in the loop, just keep it running downloading URLs as they come.

There are plenty of node js examples on online about how to spawn a child process and then catch the result as a string for your own processing. But... I want to 'interact' with a child process. For example, how would I write a node js application than starts by calling ' python ' and then types a statement ' 1+1 ', lets me catch the result ' 2 ', before proceeding to type another arbitrary statement ' 4+4 '? (And by 'type' I'm assuming it will require streaming data to the stdin that the process uses). var child = require('child_process'); var ps = child.spawn('python', ['-i']); ps.stdout

I have a script that I want to run from another one. The problem is that the child script (process) needs an user input before it continues. var child = spawn('script'); child.stdin.setEncoding('utf8'); child.stdout.on('data', function (data) { console.log(data.toString().trim()); // tells me to input my data child.stdin.write('my data\n'); }); After I input my data the child script should continue but instead it hang in there. Solution Actually the above code work for me. I'm using commander.js in the child script to prompt the user for action. Here is how I respond to a child's script prompt

I'm using lldb as a standalone debugger in OSX. I'm trying to debug a C executable, using a text file as input. The lldb documentation specifies the following command for changing stdin to a given file: process launch -i <file> Using this command, lldb seems to ignore the specified file, instead waiting for keyboard input. Is this intended behaviour? If so; what do I need to do to actually get the process to operate on my wanted input file? tl;dr: How do I get lldb to imitate a standard terminal execution like: ./executable < <file> I got it to work as follows: lldb <executable> (lldb)