Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

Paths to Enlightenment

Name: Anonymous 2009-11-02 23:56

It's helpful to think of programming languages as paths to enlightenment.

C is being a hermit in the desert. You eat grasshoppers and honey and learn to do everything with what you have.

C++ is self-flagellation locked in your chamber in the monastery. Surely if I try really hard while ignoring the pain, I will be enlightened. Re-examine my beliefs? Laughable! That would show lack of faith.

:TODO:
Python
Java
Lisp
Assembly
Delphi
J
Haskell
Smalltalk

Name: Anonymous 2009-11-04 4:34

>>12

anonymous@4chan:~$ man which

WHICH(1)                                                              WHICH(1)

NAME
       which - locate a command

SYNOPSIS
       which [-a] filename ...

DESCRIPTION
       which returns the pathnames of the files which would be executed in the
       current environment, had its arguments been  given  as  commands  in  a
       strictly  POSIX-conformant  shell.   It does this by searching the PATH
       for executable files matching the names of the arguments.

OPTIONS
       -a     print all matching pathnames of each argument

EXIT STATUS
       0      if all specified commands are found and executable

       1      if one or more specified commands is  nonexistent  or  not  exe‐
              cutable

       2      if an invalid option is specified

anonymous@4chan:~$


I could also use type but if enlightenment was an alias or a shell builtin, which is not either, it wouldn't return the path to enlightenment.

OTOH, it could be my PATH which is wrong.

anonymous@4chan:~$ find / -name "enlightenment"
anonymous@4chan:~$


No, definitely I don't have any path to enlightenment in my system. But I could make one!

anonymous@4chan:~$ touch enlightenment

Problem solved. Thread over.

Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List