Re: NSPipe
Re: NSPipe
- Subject: Re: NSPipe
- From: Daniel Todd Currie <email@hidden>
- Date: Sat, 12 Jun 2004 08:58:50 -0700
These parse errors aren't in actuality errors though. Since the string
is being sent to bc every time the user enters a character, there are
going to be piles and piles of these inevitable parse errors as they
enter their equations.
Setting to /dev/null sounds like what I want to do... Do I just put
that in a file handle, as below? What exactly is /dev/null? what is
the whole /dev directory for, for that matter? I can't even open it in
Finder, and Terminal lists all sorts of very interesting and mysterious
items. Thanks for all your help.
calculatorTask = [[NSTask alloc] init];
[calculatorTask setStandardError:[NSFileHandle
fileHandleForWritingAtPath:@"/dev/null"];
On 2004 Jun 10, at 23:45, Ben Zarzycki wrote:
On Jun 10, 2004, at 5:33 PM, Allan Odgaard wrote:
What you should probably do is instead set stderr to /dev/null.
Or if you would /like/ to save the errors instead of tossing them,
save them to somewhere the consumer could access easily to help you
debug (in case they do run into a legitimate problem). Such as
~/Library/Application\ Support/MyApp/error.log
Better to keep error logs in my opinion.
-Ben
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
| References: | |
| | >NSPipe (From: Daniel Todd Currie <email@hidden>) |
| | >Re: NSPipe (From: Allan Odgaard <email@hidden>) |
| | >Re: NSPipe (From: Ben Zarzycki <email@hidden>) |