Well, you make two very strong assumptions.
First, that your readers start in the beginning and read to the
end.
Second, that your readers are sufficiently dedicated to learn
your terminology.
The first is false: I got to that page via Google.
The second is only true in varying degrees,
and I wo
Well, you make two very strong assumptions.
First, that your readers start in the beginning and read to the
end.
Second, that your readers are sufficiently dedicated to learn
your terminology.
The first is false: I got to that page via Google.
The second is only true in varying degrees,
and I wo
Greg Kochanski wrote:
> Well, I don't know how it can be precise
> and correct when it has dangling antecedents.
> Gramatically speaking, that's the equivalent of
> an uninitialized pointer.
I don't think there is anything "dangling" there. What the paragraph
assumes (and quite patently wrongly)
Well, I don't know how it can be precise
and correct when it has dangling antecedents.
Gramatically speaking, that's the equivalent of
an uninitialized pointer.
However, I agree with you that it probably just
needs a minor bit of fiddling to make sure it
answers "Instead of what?" and "Earlier tha
[EMAIL PROTECTED] wrote:
> Full_Name: Greg Kochanski
> Version: 2.2.0
> OS: Debian Linux i686
> Submission from: (NULL) (212.159.16.190)
>
>
> In /usr/share/doc/r-doc-html/manual/R-data.html (at least that's where
> it is on Debian...) the documentation is unclear. Comments below.
The document
Full_Name: Greg Kochanski
Version: 2.2.0
OS: Debian Linux i686
Submission from: (NULL) (212.159.16.190)
In /usr/share/doc/r-doc-html/manual/R-data.html (at least that's where
it is on Debian...) the documentation is unclear. Comments below.
The paragraph has unclear references, and I have no
