[Moved this to gpc-doc]
On 03:52 03/06/04, Frank Heckenbach wrote:
While we're at it, could anybody please kindly update all the other parts of the documentation that need updating (mostly programming and reference)? :-)
Since I'm working on an OO project right now, I guess I have a moral obligation to update the OO-related areas. I'm working on some of the OO-related Reference items (in particular, `private', `protected' and `public'), although I can't say it's easy, considering:
1) I have never worked with and so don't know Texinfo, and I'm figuring things out as I go along; and, 2) Most of what I know about OO Pascal comes from Borland, and I can't exactly copy stuff from their textbooks.
Diffs to the archive you've uploaded will come in as soon as I've made significant changes.
Neil Santos wrote:
Since I'm working on an OO project right now, I guess I have a moral obligation to update the OO-related areas. I'm working on some of the OO-related Reference items (in particular, `private', `protected' and `public'), although I can't say it's easy, considering:
- I have never worked with and so don't know Texinfo, and I'm
figuring things out as I go along; and,
- Most of what I know about OO Pascal comes from Borland,
That's good since GPC's model is mostly like Borland's. (BP doesn't have `protected' AFAIR, and there are some other GPC extensions such as `is' and `as', but generally OOP is one the areas where BP knowledge helps most.)
and I can't exactly copy stuff from their textbooks.
No. In fact you shouldn't even look at the textbooks during the time you write something and some time before to avoid "mental copying" ...
Diffs to the archive you've uploaded will come in as soon as I've made significant changes.
Thanks.
Frank
On 15:34 08/06/04, Frank Heckenbach wrote:
- Most of what I know about OO Pascal comes from Borland,
That's good since GPC's model is mostly like Borland's. (BP doesn't have `protected' AFAIR, and there are some other GPC extensions such
No; I think Delphi has it, though.
as `is' and `as', but generally OOP is one the areas where BP knowledge helps most.)
Well, it's technically good as, like you've said, GPC's current object implementation is similar to Borland's; but it's practically bad, because we're trying to write a free manual here. ;)
and I can't exactly copy stuff from their textbooks.
No. In fact you shouldn't even look at the textbooks during the time you write something and some time before to avoid "mental copying"
Yes, I know; I've read it in an FSF paper--the Coding Standard, I believe. I remember reading a few tips on how to go about your work, if you *vaguely* remember reading another work, but it's of little use for writing free manuals.
After all, the CS deals with code, and `[organizing] internally along different lines' is something that doesn't mean much for English sentences. :D
Diffs to the archive you've uploaded will come in as soon as I've made significant changes.
Thanks.
Thank me when I've sent diffs in--and not even then, since I'm merely doing my job. :)
After all, the CS deals with code, and `[organizing] internally along different lines' is something that doesn't mean much for English sentences. :D
I think it's a common situation with technical documentation, whether free or proprietary. Most people who write some have read some before.
I even think it's easier to formulate differently in language than in programming ...
Frank
-
Frank Heckenbach -
Neil Santos