Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

In SCAN why do we need to user console.error("end"); instead of console.log? #8

Open
yanndebelgique opened this issue Nov 30, 2014 · 2 comments

Comments

@yanndebelgique
Copy link

Why ?

res.on("end", function (e) {
  console.error("done!");
});

Why is this not ok?

res.on("end", function (e) {
  console.log("done!");
});
@othiym23
Copy link
Owner

othiym23 commented Dec 1, 2014

Because the idea is to separate your diagnostic output from your program's expected output – console.log and console.error print their results to different file descriptors (stdout and stderr, respectively). Is that unclear from the text in the workshopper?

@yanndebelgique
Copy link
Author

apparently not but im just one reference point so... thank you for the tutorials btw!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants