Re: Cocoa Newbie Question.

On Jun 12, 3:14 pm, Gregory Weston <u...@xxxxxxxxxx> wrote:
In article
<776e7be9-1443-4852-9860-dbf6b3537...@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>,



 piscesboy <oraclmas...@xxxxxxxxx> wrote:
On Jun 12, 1:11 pm, Gregory Weston <u...@xxxxxxxxxx> wrote:
In article
<181e54c6-6c74-4b5e-b355-a28f5b6a6...@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>,

 piscesboy <oraclmas...@xxxxxxxxx> wrote:
On Jun 12, 8:24 am, Dave Seaman <dsea...@xxxxxxxxxxxx> wrote:
On Wed, 11 Jun 2008 22:05:19 -0700 (PDT), piscesboy wrote:
On Jun 11, 10:18 pm, Dave Seaman <dsea...@xxxxxxxxxxxx> 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 just *love* people who think it's their right to educate other people
as to what their own motivations were. Congratulations on virtually
ensuring that you're not going to get help for your next Cocoa newbie
question. Very efficient of you.

Congratulations on having one less poster here on mac.programmer.help.

Doesn't fuss me one bit when that poster is hostile, egotistical and
needy all at once.

You didn't have to join in on this but apparently you are another one
of those posters with nothing better to do but assert your superiority
on other people asking for help by ganging up with another poster to
berate them for not being omnicient knowers of all things Cocoa/mac
whatever.

Your level of knowledge of Cocoa and the Mac has nothing to do with my
reasons for chastising you. ("Berate" isn't actually the appropriate
word there. If you can understand why, you're well on your way to the
attitude adjustment you need.)

This post could have just ended 5 posts back but everyone
here has nothing better to do than insult anyone else's intelligence.

Wait. Stop right there.

I want you to look back at this thread - this mess that *you* started -
and find a single place where your *intelligence* was insulted. Or
commented on in any way, for that matter.

Are you blind, Greg?

"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. "

Now who wrote that? Hmmm...looking at the author of the thread I have
to conclude that Dave wrote that. And is it before or after my thread?
By the looks of it it appeared well before mine. You say you have
trouble with people who try to assume the motives of other posters on
this board and you say nothing about what Dave posted before me. So,
if you want to stop acting like a bigot and sticking up for your
boyfriend, you should listen to my argument. He was responding to my
thread which assumed I wasn't bright enough to run my program using
proper syntax which is extremely condescending. I'd be happy to carry
this argument as far as you're willing.




You can't. Never happened. I wouldn't be surprised if you *think* it
happened, because based on your responses - all we have by which to
judge, after all - you seem to keep misunderstanding what Dave (and now
I) actually said.

--
"Harry?" Ron's voice was a mere whisper. "Do you smell something ... burning?"
   - Harry Potter and the Odor of the Phoenix

.

Relevant Pages

  • Re: Cocoa Newbie Question.
    ...  Don't be surprised if executing the program appears to produce ... no response at all, since "test" is a shell builtin. ... between an executable C file and a shell command, ...
    (comp.sys.mac.programmer.help)
  • Re: Cocoa Newbie Question.
    ...  Don't be surprised if executing the program appears to ... no response at all, since "test" is a shell builtin. ... Congratulations on having one less poster here on mac.programmer.help. ...
    (comp.sys.mac.programmer.help)
  • Re: Cocoa Newbie Question.
    ...  Don't be surprised if executing the program appears to ... since "test" is a shell builtin. ... I have exactly 24 hours worth of Objective-C ... Congratulations on having one less poster here on mac.programmer.help. ...
    (comp.sys.mac.programmer.help)
  • subject to Melves unconscious trend
    ... Where Dilbert's recent disappointment guarantees, ... They are executing on board top, in disciplinary, ... cover me celebrating in response to your thick post. ... Almost no apartments will be fatal confidential whales. ...
    (sci.crypt)
  • Well Atiqullah will mark the gold, and if Ramez enormously possesses it too, the period will spoil b
    ... Her conception was asian, hard, and ... invites in back of the shell. ... when John executes the many punch instead of the ... with environmental, at all disabled, in response to possible ...
    (sci.crypt)