On Thu, 12 Jun 2008 09:07:43 -0700 (PDT), piscesboy wrote:
> On Jun 12, 8:24 am, Dave Seaman <dsea...@[EMAIL PROTECTED]
> wrote:
>> On Wed, 11 Jun 2008 22:05:19 -0700 (PDT), piscesboy wrote:
>> > On Jun 11, 10:18 pm, 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
executable
>> >> >> program. Don't be surprised if executing the program appears to
produce
>> >> >> no response at all, since "test" is a shell builtin.
>> >> > It is in fact a "test". A dummy program that I built to learn
about
>> >> > 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
choice
>> >> for naming an executable program. 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.
>>
>> > Evidently, you don't understand the difference between an executable
C
>> > file and a shell command.
>>
>> I learned that difference around 1980. It's the difference I was
trying
>> 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". And since your
first
>> 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".
[orion:~] $ type test
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. I 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?
--
Dave Seaman
Third Circuit ignores precedent in Mumia Abu-Jamal ruling.
<http://www.indybay.org/newsitems/2008/03/29/18489281.php>
|
