Sorry, I apologize for all the confusion. I will try to remedy it here: When you receive a program in *source code* form, you would type it into Bash as follows:
cat <<'EOF' | tee [file name] | bash type your script here EOF Then Bash runs the script. When you receive a program in *object code* form, you would type it into an object code editor and then save it in a binary file. You would then run `chmod +x' on that binary file and then tell Bash to execute it (as *opposed* to interpreting a Bourne Shell script), hoping you didn't make a mistake. If you did make a mistake, then hopefully the author might have provided a SHA1 checksum against which you can compare the SHA1 checksum of the file you typed. If they don't match, then you made a mistake and you must compare (and you know how slow that is!) that file against the print in the aggregate, making sure they match, before executing the program again. Again, I apologize for the confusion. On Mon, Jan 26, 2015 at 12:29 PM, Eduardo A. Bustamante López < dual...@gmail.com> wrote: > I'd suggest first investigating how bash works (read the source), before > claiming funky stuff. Bash interpretes *source code*, it doesn't matter > how you > provide it. The only exception is what Greg specified. > -- Ryan Cunningham
