It's UWAweek 48

help2003/help4407

This forum is provided to promote discussion amongst students enrolled in Open Source Tools and Scripting.

Please consider offering answers and suggestions to help other students! And if you fix a problem by following a suggestion here, it would be great if other interested students could see a short "Great, fixed it!"  followup message.

How do I ask a good question?
Displaying the 3 articles in this topic
Showing 3 of 564 articles.
Currently 3 other people reading this forum.


 UWA week 14 (1st semester, week 6) ↓
SVG not supported

Login to reply

👍?
helpful
5:51pm Tue 5th Apr, Ashley F.

I was just looking to confirm if it matters whether we follow the labs or the lectures for things like: Using #!/usr/bin/env bash instead of #!/bin/bash and Using 1>&2 echo or echo "" > /dev/stderr Thank you


SVG not supported

Login to reply

👍?
helpful
6:24pm Tue 5th Apr, Ryan B.

"Ashley Ford" < @student.uwa.edu.au> wrote:

I was just looking to confirm if it matters whether we follow the labs or the lectures for things like:

Using #!/usr/bin/env bash instead of #!/bin/bash

and

Using 1>&2 echo or echo "" > /dev/stderr

Thank you

Hi Ashley,

I'm going to be "that teacher" and ask: have you looked into what the differences are between the examples you have given (if any)?

If there are differences between the two, it may very well matter! However, it may also be contextual as to whether it does matter (or not). The best way to evaluate if (potential) differences matter is to know what the differences are, and work accordingly. :)

(Removes "that teacher" hat, puts on "fellow postgrad" hat): This may help get the ball rolling for your second example: https://unix.stackexchange.com/questions/274042/sending-output-to-dev-stderr-vs-2.

Hope this helps!


SVG not supported

Login to reply

👍?
helpful
7:02pm Tue 5th Apr, Michael W.

Hi Ashley, Ryan is, of course, absolutely right; they do identical things and it's a matter of style. Here is why I make the choices I do: *) I prefer #!/usr/bin/env bash (in this case, python, whatever) because it relies on exactly one program being we were expect to it to be: env. From then on, all the other interpreters, etc, can move. *) I prefer > /dev/stderr as the way to direct a print statement (say) because it;s more obvious to the reader that 1>&2 (dup file descriptor 1 to file descriptor 2).

As they say, you pays your money, you makes your choice (just be consistent).

Cheers MichaelW

The University of Western Australia

Computer Science and Software Engineering

CRICOS Code: 00126G
Written by [email protected]
Powered by history
Feedback always welcome - it makes our software better!
Last modified  1:17AM Sep 14 2022
Privacy policy