It isn't clear to me what I should do to get the optional ExamineData structure from IDOS->MatchFirst() and IDOS->MatchNext() calls. The fact that it's explicitly stated in the AllocDosObject() that allocating an ExamineData this way is only for handlers and filesystems suggests to me that this is not the way to go at least.
I want the ExamineData instead of FileInfoBlock because I want my code to support large files as well as filenames longer than 107 characters.
it would be nice if the coding tool section would grow.
I miss an hint to "tIDE", a tiny IDE for the "quick compile" which I used the last few weeks to do some minor stuff (i.e compiling examples from the Developer CD). It can be found here: http://os4depot.net/index.php?function=showfile&file=development/ide/tide.lha
(Since my news item is taking too long to be approved, I'm posting this here)
I am releasing a "full preview" of the next version of the PortablE programming language. It is now aimed at beginners & those new to the E language. Previous releases of PortablE were aimed at existing AmigaE users, and those familiar with AmigaOS programming. But after more than a year of development, PortablE is much easier for beginners to pick-up & play with:
Hello to all.
I would like to ask you if it is better to use the old classic encoded prefs files for storing the preferences of our own programs, or the new XML files that was introduced with OS4.
I'm sure both have advantages and disadvantages, but what you prefer? What should new programmers like me prefer?
Great forum you have here, I hope it starts coming to life soon. In the meantime... I have been looking across various Amiga sites and there are plenty of libraries X, Y and Z, but for beginners little documentation of how to quickly get started and up and running.
I am hoping to start work on a medium-sized project this year when AVD and the X1000 arrives and I need to know a few fundamental principles and common routines.
