Re: Martin Harvey -- Thread Tutorial

um ive found a few more little errors -- if you want to hear them post away
if not then ill keep them to my self.

On Sat, 30 Aug 2003 23:01:25 GMT, "name" <e@m.a> wrote:

>um ive found a few more little errors -- if you want to hear them post away
>if not then ill keep them to my self.

HA! I know that there are precisely 3 error in the entire tutorial of
any significance.

One is in the changelog, where I comment about having added a chapter,
and promptly get the chapter name wrong.

Another is in the narrative somewhere, where a reference a nonexistent
diagram, somewhere around chapter 5 or 6,

The third is the fact that when talking about threads and database
access, my conditions for correct database functioning are not strict
enough.

Many other people have reviewed the guide and not found any other
significant errors. If you think you've found some, then feel free to
point them out, but I'd like to remind you if that if you find a whole
bunch of "nonexistent" errors, it aint gonna make you look too good in
front of everyone else.

MH.

<snip>

Before I start posting your errors please define:

1.) Errors of any significance
2.) "nonexistent" errors

"name" <e@m.a> wrote in message
news:evb4b.7592$Om1.1120@newsread2.news.atl.earthl ink.net...
>
> "Martin Harvey" <martin@pergolesi_nospam_.demon.co.uk> wrote in message
> news:jgg2lvc7vth267v1bq61no32lu3pi9i62p@4ax.com...
> > On Sat, 30 Aug 2003 23:01:25 GMT, "name" <e@m.a> wrote:
> >
> > >um ive found a few more little errors -- if you want to hear them post
> away
> > >if not then ill keep them to my self.
> >
> > HA! I know that there are precisely 3 error in the entire tutorial of
> > any significance.
> >
> > One is in the changelog, where I comment about having added a chapter,
> > and promptly get the chapter name wrong.
> >
> > Another is in the narrative somewhere, where a reference a nonexistent
> > diagram, somewhere around chapter 5 or 6,
> >
> > The third is the fact that when talking about threads and database
> > access, my conditions for correct database functioning are not strict
> > enough.
> >
> > Many other people have reviewed the guide and not found any other
> > significant errors. If you think you've found some, then feel free to
> > point them out, but I'd like to remind you if that if you find a whole
> > bunch of "nonexistent" errors, it aint gonna make you look too good in
> > front of everyone else.
> >
> > MH.
>
> Um there are a bunch like ",dD" ^_^ -- it will make you look bad if i
post
> all these errors though.
>
>
Ex of the errors im finding:
(http://www.pergolesi.demon.co.uk/prog/threads/Ch3.html)
"First of all, it is worth know exactly what state is stored..."
worth know should be worth knowing

"Nicholas Sherlock" <N_sherlock@hotmail.com> wrote in message
news:birgqp$4v1$1@lust.ihug.co.nz...
> name wrote:
>
> > Um there are a bunch like ",dD" ^_^ -- it will make you look bad if
> > i post all these errors though.
>
> Erm.. I think it would make *you* look bad if you posted them.
Well thats why I asked first... i really could care less how i "look" on a
ng.

> Typos don't
> count as errors.
lol ok! lets see if MH agrees. If hes a perfectionist or wants his tutorial
to be book quiality he will be estatic about me finding / reporting errors.
(typos are errors in my world)

> Cheers,
> Nicholas Sherlock
>
>

Nicholas Sherlock wrote:
> Erm.. I think it would make *you* look bad if you posted them. Typos don't
> count as errors.

A typo is, by definition, an error. Maybe not an error of significance
in a tutorial on threading, though, and certainly not an error worth
discussing on a public forum about Delphi.

--
Rob

Rob Kennedy wrote:
> Nicholas Sherlock wrote:
>> Erm.. I think it would make *you* look bad if you posted them. Typos
>> don't count as errors.
>
> A typo is, by definition, an error. Maybe not an error of significance
> in a tutorial on threading, though, and certainly not an error worth
> discussing on a public forum about Delphi.

In this situation, wouldn't errors be more like, saying incorrect things
about threads or posting incorrect code?

Cheers,
Nicholas Sherlock

<snip>
"and certainly not an error worth
discussing on a public forum about Delphi."

I agree, the wonders of e-mail -- it would be neat if people had instant
messengers.

"Nicholas Sherlock" <N_sherlock@hotmail.com> wrote in message
news:bis3us$iem$1@lust.ihug.co.nz...
> Rob Kennedy wrote:
> > Nicholas Sherlock wrote:
> >> Erm.. I think it would make *you* look bad if you posted them. Typos
> >> don't count as errors.
> >
> > A typo is, by definition, an error. Maybe not an error of significance
> > in a tutorial on threading, though, and certainly not an error worth
> > discussing on a public forum about Delphi.
>
> In this situation, wouldn't errors be more like, saying incorrect things
> about threads or posting incorrect code?

I think they are talking about incorrect content vs. a typo - to me an error
is an error.


> Cheers,
> Nicholas Sherlock
>
>

On Sun, 31 Aug 2003 13:29:03 GMT, "name" <e@m.a> wrote:
>^_^ then can i cash in my credit for some thread help once i attempt to put
>my timer in one?

Yeah, but I don't think you'll be needing much help on that topic...

"Martin Harvey" <martin@pergolesi_nospam_.demon.co.uk> wrote in message
news:rc44lvgaa3kteldb0gjqbb5e12lru8el7g@4ax.com...
> On Sun, 31 Aug 2003 13:29:03 GMT, "name" <e@m.a> wrote:
> >^_^ then can i cash in my credit for some thread help once i attempt to
put
> >my timer in one?
>
> Yeah, but I don't think you'll be needing much help on that topic...

See "My First Thread"

name wrote:
> <snip>
> "and certainly not an error worth
> discussing on a public forum about Delphi."
>
> I agree, the wonders of e-mail

Then why didn't you intiate this discussion with Martin over e-mail
instead of posting here?

--
Rob

Nicholas Sherlock wrote:
> Rob Kennedy wrote:
>>A typo is, by definition, an error. Maybe not an error of significance
>>in a tutorial on threading, though, and certainly not an error worth
>>discussing on a public forum about Delphi.
>
> In this situation, wouldn't errors be more like, saying incorrect things
> about threads or posting incorrect code?

Those would be errors, and typos would be errors. The ones you mention
would be appropriate topics for this newsgroup, whereas typo discussions
would be more appropriate on, say, alt.usage.english.

If someone posted a message here soliciting comments on a technical
article, I would probably include comments on spelling errors or
apostrophe misuse, but if the only flaws I found were of that nature,
then my comment would probably compliment the writer on the article but
mention a handful of the errors and invite follow-up discussion by
e-mail. Typos can distract readers from the real content of the writing,
and so they are worth fixing, but if the writer hasn't asked for
comments, then mentioning those kinds of mistakes is rude.

--
Rob

On Sun, 31 Aug 2003 14:46:30 -0500, Rob Kennedy <rkennedy@example.com>
wrote:

>Then why didn't you intiate this discussion with Martin over e-mail
>instead of posting here?

Cos then he'd have to give out a valid e-mail address ;-)

MH.

"Martin Harvey" <martin@pergolesi.demon.co.uk> wrote in message
news:slp4lvonm5tbo43tcj6p0f1a58j3ba23ir@4ax.com...
> On Sun, 31 Aug 2003 14:46:30 -0500, Rob Kennedy <rkennedy@example.com>
> wrote:
>
> >Then why didn't you intiate this discussion with Martin over e-mail
> >instead of posting here?
>
> Cos then he'd have to give out a valid e-mail address ;-)

lol....
1.) mh please look at my "My First Thread" thread please!
2.) is martin@pergolesi.demon.co.uk your email? I can make a free yahoo
email and go through a few proxys and send you my list of errors.


>
> MH.
>