On Jun 12, 12:32=A0pm, Dave Seaman <dsea...@[EMAIL PROTECTED]
> wrote:
> On Thu, 12 Jun 2008 09:07:43 -0700 (PDT), piscesboy wrote:
> > On Jun 12, 8:24=A0am, Dave Seaman <dsea...@[EMAIL PROTECTED]
> wrote:
> >> On Wed, 11 Jun 2008 22:05:19 -0700 (PDT), piscesboy wrote:
> >> > On Jun 11, 10:18=A0pm, Dave Seaman <dsea...@[EMAIL PROTECTED]
> wrote:
> >> >> On Wed, 11 Jun 2008 19:05:58 -0700 (PDT), piscesboy wrote:
>
> >> >> >> By the way, "test" is a very poor choice for the name of an
execu=
table
> >> >> >> program. =A0Don't be surprised if executing the program appears
t=
o produce
> >> >> >> no response at all, since "test" is a shell builtin.
> >> >> > It is in fact a "test". =A0A dummy program that I built to learn
a=
bout
> >> >> > Objective-C. It isn't meant to be proprietary software or a
final
> >> >> > release at all. I have exactly 24 hours worth of Objective-C
> >> >> > experience as of this posting, so I am very much a novice at
this
> >> >> > stuff.
>
> >> >> Evidently you didn't read my explanation of why "test" is a poor
cho=
ice
> >> >> for naming an executable program. =A0I was not suggesting anything
a=
t all
> >> >> about what kind of program it is, but only what is likely to
happen =
when
> >> >> you type "test", expecting this to run your program.
>
> >> > Evidently, you don't understand the difference between an
executable =
C
> >> > file and a shell command.
>
> >> I learned that difference around 1980. =A0It's the difference I was
try=
ing
> >> to explain to you, but it went over your head on the first try.
> > LOL I wasn't even born in 1980 and I still understood it not even out
> > of high school. And, no, you weren't trying to explain the difference
> > between an executable C file and a shell command, I did that to you
> > after your ignorant post. What you were doing was trying to exert your
> > superiority over someone who was asking for your help just like you're
> > doing now. It's posts like this that make me hate using usenet and
> > interacting with people like you.
>
> >> > I don't type "test" to run my program, I
> >> > type "./test". I could just as easily have named my executable
"grep"=
> >> > and run it by typing "./grep" and no confusion would result.
>
> >> A person who is struggling with link commands such as you were is
quite=
> >> likely to be unaware of the need to type "./test". =A0And since your
fi=
rst
> >> response completely missed the point of what I was saying, I thought
it=
> >> necessary to try again.
> > I was asking a question about one linking command for a language I
> > never used before. Your response clearly showed you can't tell the
> > difference between "test" and "./test" one being a shell command and
> > one being an executable C file. Why would anyone confuse the two
> > unless you assume they are of the same intelligence level as you are?
> > 1980? You need to go back to school or something if you can't tell the
> > difference up to now.
>
> Evidently you don't know what a "shell builtin" is, or you think it's
> something different from what you are calling a "shell command".
>
> =A0 =A0 =A0 =A0 [orion:~] $ type test
> =A0 =A0 =A0 =A0 test is a shell builtin
>
> Since you have quoted my exact words, all you need to do is look up
above
> and notice where I used the term "shell builtin" when I was explaining
> why the choice of the name "test" might be a bad idea for an executable
> program. =A0I drew a clear distinction between the two concepts, but you
> responded as if I were merely criticizing your terminology instead of
> pointing out the possibility of unexpected behavior.
>
> If you had merely meant to say that you understood the problem and knew
> how to avoid it, then why didn't you just say so in the first place
> instead of responding as if you had completely failed to comprehend the
> point?
No, these are your exact words, Dave:
" I was not suggesting anything at all
about what kind of program it is, but only what is likely to happen
when
you type "test", expecting this to run your program."
Then I responded by saying that that is NOT how I run my program, I
type "./test" not "test" as you thought I did. Then I responded that
that is not how I run my program and the discussion should have ended
there but no...you clearly assumed I would not know the difference
between the two by saying the previous post of yours went over my head
which is intellectually insulting.
Whether or not "test" is a shell builtin is irrelevant since it is
distinguished from the executable I am running.
>
> --
> Dave Seaman
> Third Circuit ignores precedent in Mumia Abu-Jamal ruling.
> <http://www.indybay.org/newsitems/2008/03/29/18489281.php>
|
