It's not an area that I'm competent to comment on, beyond thanking you for
your rigorous look at this.
Jon
On Mon, 18 Oct 2021, 12:10 Rony G. Flatscher, <rony.flatsc...@wu.ac.at>
wrote:
> Sleeping over the current structure of the API samples these are the
> things that are in place currently:
>
> 1. samples/Makefile.am (???)
> 2. samples/native.api/call.example/ ... for all systems,
> CMakeLists.txt, Makefile.linux, Makefile.windows, Makefile.am (???)
> 3. samples/unix/api/callrexx/ ... callrexx1.cpp, callrexx2.c,
> CMakeLists.txt, no Makefiles
> 4. samples/unix/api/wpipe{1..3}/... rexxasp{1..3}.c,
> aspitest{1..3}.rex, CMakeLists.txt, no Makefiles
> 5. samples/windows/ ... api/ ... misc/ ... ole/ ... oodialog/
> ...rexutils/
> 6. samples/windows/api/ ... callrxnt/ ... callrxwn/ ... rexxexit/
> 7. samples/windows/api/wpipe{1..3}/ .. rexxapi{1..3}.c,
> apitest{1..3}.rex, CMakeLists.rex, nmake make files named rexxapi{1..3}.mak
>
> Suggested changes:
>
> 1. It seems that the "Makefile.am" files are left-overs and can be safely
> deleted?
>
> 2. create a new structure for the installed api samples, such that the
> installation on all systems would look like:
>
> samples/api
> samples/api/classic/ ... having all samples in their own directories that
> exemplify the SAA API interface, rexxapi.pdf, "Chapter 2. Classic Rexx
> Application Programming Interfaces"
> samples/api/c++/ ... having all samples in their own directories that
> exemplify the ooRexx native API interface, rexxapi.pdf, "Chapter 1. Rexx
> C++ Application Programming Interfaces"
>
> 3. rename "wpipe{1..3}" directory names to "rexxapi{1..3]" to match the
> names of the programs therein for all systems ("wpipe" is confusing)
>
> 4. Unix, rename "rexxsp{1..}.c" to "rexxapi{1..3}.c" and
> "aspitest{1..3].rex" to "apitest{1..3].rex" to match the Windows names
> ("asp" does not make any sense in this context); sample change done with
> "wpipe1"
>
> 5. Add Makefiles where there are missing, such that interested programmers
> can try compiling and running the samples on their own (e.g. missing for
> the Unix wpipe samples
>
> 6. Add "readme.txt" files in each api directory to briefly describe its
> content
>
> In addition I propose to add the c++ samples of the 2015 RexxLA
> presentation of how to create external routines and external methods, cf.
> <https://www.rexxla.info/events/2015/schedule.html>
> <https://www.rexxla.info/events/2015/schedule.html>, the talk with the
> code samples entitled "How to Develop a Native Library in C++ for ooRexx in
> a Nutshell".
>
> The easier it becomes for programmers to understand how the APIs work the
> better.
>
> Any comments?
>
> ---rony
>
>
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
