08 August 2011, 15:50 | #41 |
Join Date: Jul 2008
Location: Sweden
Posts: 2,269
|
I appreciate this and use it now and then, too. It's great to have it all in one place with a search function. Thanks
|
24 June 2012, 12:13 | #42 |
Registered User
Join Date: Oct 2011
Location: At home :)
Posts: 18
|
Nice to have indeed, thank you
|
09 March 2023, 19:50 | #43 |
Registered User
Join Date: Jan 2023
Location: Nice, France
Age: 55
Posts: 13
|
Thanks a lot. This is very useful, even after all these years
|
27 April 2023, 02:06 | #44 |
Registered User
Join Date: May 2022
Location: Adelaide, South Australia, Australia
Posts: 209
|
The two most useful reasources for me when learning to program on the Amiga:
1. These documents and includes, they're so useful! 2. English Amiga Board for when I have no clue what I'm doing. |
27 April 2023, 14:51 | #45 |
Zone Friend
Join Date: May 2006
Location: France
Posts: 1,894
|
Amiga developer CD 2.1 too, I hope that Olsen he’s still working on improving developer material.
|
08 July 2023, 08:43 | #46 | |
Registered User
Join Date: Aug 2010
Location: Germany
Posts: 546
|
Quote:
While this material, which came from the Amiga Developer CD 2.1 (I compiled that), is old, it's good that it is available in the first place. But it is painful for me to see that this documentation has aged so poorly. The Amiga ROM Kernel manual contents are an adaptation of the contents of the CATS Developer CD V2.0 from 1992, with the original manuscript text converted manually into the 1991 AmigaGuide format. I wrote the tools which converted them into HTML5 files, and they are available in this form on the web site. Let that sink in for a moment... We ought to have something better than this, both in terms of what is available to developers, as well as what it contains. For example, there is no AmigaDOS documentation on the Amiga Developer CD 2.1 comparable in scope and quality to the Amiga ROM Kernel manual contents because none was available on the CATS Developer CD V2.0. How to dissuade anybody from trying to develop software for the Amiga? Make her or him start by exploring the wonders of using the dos.library - works every time Last edited by Olaf Barthel; 08 July 2023 at 16:51. |
|
08 July 2023, 09:05 | #47 | |
Registered User
Join Date: Aug 2010
Location: Germany
Posts: 546
|
Quote:
Unless something unexpected happens, you may be able to look forward to see a major rework of the dos.library AutoDocs. The documentation has been reformatted to improve accessability. More bugs recently discovered (some of them are more than 30 years old) and fixed are now covered in the documentation. There is a completely new introduction to dos.library and its underpinnings, with a large section covering the limitations, unexpected constraints (e.g. stack size requirements, path length limitations and silent truncation) and even advice on what to watch out for, if you want to stay on dos.library's good side (if there is one; this is still part of cutting-edge research). Every single AutoDoc entry for dos.library has been updated and the relevant data structures, e.g. used by Lock(), Open(), Examine(), Info(), are covered in context. The AutoDoc entries now feature new sections ("warnings" and "notes"), where needed, which describe what pitfalls lie ahead and which complex problems you might face. For example, NameFromLock() can produce path names which will be longer than Open(), Lock() or Rename() can handle. These warnings are repeated in the respective entries, rather than collected in one single section, so that you can look up the respective function and see what might be in store for you. The AutoDocs are supposed to be brief and to the point, but dos.library is arguably an exception. Next to graphics.library, it contains the most complex of the AmigaOS APIs, some of which are poisonously easy to get wrong ever so slightly (such as ExAll()). The corresponding 'C' header files have been reformatted and updated in order to make them more accessible and provide more context. For example, the relationship between the DosPacket types and the dos.library functions is documented now. These changes to the dos.library documentation spilled over into exec.library and expansion.library documentation changes, too. Last edited by Olaf Barthel; 30 July 2023 at 09:54. Reason: Was getting ahead of myself: NDK 3.2R4 is the current release, not R5 |
|
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Manuals online | Stedy | support.Hardware | 5 | 22 September 2009 09:44 |
FS: Soundscape & Dr T. music software manuals | coze | MarketPlace | 0 | 12 February 2007 13:22 |
I need amiga & Workbench Manuals! | filippodb | support.Hardware | 5 | 22 January 2006 20:35 |
Includes & Autodocs | Jherek Carnelia | request.Apps | 7 | 12 March 2002 00:09 |
Manuals for Sinbad & Vendetta | Minuous | support.Games | 3 | 23 October 2001 07:37 |
|
|