This is not a moan or a complaiint! It's sort of a heartbreaker though, and a suggestion.
I spent some time yesterday trying to understand my own problems with using the FPC/Lazarus docs, and asking myself what I'd point someone new to FPC/Lazarus toward if (s)he had just started using the system and was trying to get familiar with the very rich body of documentation and other information that's available on-line.
The best "starting point" I found in poking around was
https://wiki.freepascal.org/Lazarus_Documentation#Free_Pascal_Compiler_DocumentationThere is a lot of terrific information here (a little overwhelming, in fact! Need a "guide to the guide to the guide!) But thinking about my new user again and consistent with this thread, I thought I'd encourage him to scroll down to "Free Pascal Compiler Documentation" and at least get aware of the content of the material linked to there for a start. In particular taking a look in "Reference guide to the system unit" and the "Run-Time Library reference manual."
I clicked on the first link and got this
An error has been encountered in accessing this page.
1. Server: lazarus-ccr.sourceforge.io
2. URL path: /fpcdoc/ref/ref.html
3. Error notes: NONE
4. Error type: 404
5. Request method: GET
6. Request query string: NONE
7. Time: 2024-07-16 15:30:05 UTC (1721143805)
Reporting this problem: The problem you have encountered is with a project web site hosted by SourceForge.net. This issue should be reported to the SourceForge.net-hosted project (not to SourceForge.net).
...
The same message appears if I try the link to the RTL manual, but I know it's there on-line in it's latest version at
https://www.freepascal.org/docs-html/current/.I also noticed that all of the .PDF docs I have on my computer are dated 2017 while the current on-line manuals are dated 2021 -- my problem of course and nothing to do with FPC/Lazarus.
Not sure what the moral of this story is. Maybe though, it would be helpful to put a new topic in the "Programming" section of the forum here, named something like "Explore the Documentation" (rather than RTFM, which shows up here, sadly, from time to time) where the state of all the docs could be highlighted and addressed. The docs are as important as the code, right?