Dear Harmander, thank you for the idea of leaving the name "rexxpg", which I just did. So if using the Dopbox link below there will be a "rexxpg.pdf" file there which represents the primer.
Cheers ---rony On 03.03.2020 04:31, Harmander Singh wrote: > Excellent! It might be better to retain the name rexxpg for the primer, in > line with traditional > language doco. > > Harmander Singh > > On Tue, 3 Mar 2020 at 08:26, Jon Wolfers <[email protected] > <mailto:[email protected]>> wrote: > > +1 > > This makes sense to me. > > Jon > > On Mon, 2 Mar 2020 at 18:54, Rony G. Flatscher <[email protected] > <mailto:[email protected]>> wrote: > > For almost decades it has irritated me that the "rexxpg.pdf" book > would contain a primer > to ooRexx and the native APIs. The former would be helfpul for anyone > who wants to learn > ooRexx, the latter is only helpful for people who have expert > knowledge on C++ (and > ooRexx) and C. > > So I tried to split the book 'rexxpg.pdf' into two different ones, > one 'rexxprimer.pdf' > and another one 'rexxapi.pdf'. > > The result can be temporarily looked at my Dropbox (same link as for > the rexxref.pdf with > the EventSemaphore and MutexSemaphore documentation for which a patch > was supplied > yesterday to the ooRexx project): > > > <https://www.dropbox.com/sh/gxvvgskb04gdsqf/AACRo_ZLeFOdoBXUHroPY_-Ca?dl=0> > > <https://www.dropbox.com/sh/gxvvgskb04gdsqf/AACRo_ZLeFOdoBXUHroPY_-Ca?dl=0> > > What do you think? > > ---rony >
_______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
