Hi Uli
But an occasional crash doesn't sound too bad, so I left rxapi as daemon.
> There is a segmentation fault after re-tokenisation, but it doesn't kill
> rxapi.
>
I'm curious to know : how often do you have crashes when using your build
? I re-tested today under Puppy, running functional-test.rex. When the
modified rxapi is started as a daemon, I have a crash on one of the two
executions.
> I had some basic problems configuring the installation, so I put the
> changes
> as patch under http://sourceforge.net/support/tracker.php?aid=3469313.
>
Thanks a lot for this patch.
I'm not used to work with Linux and the automated build, so it was
interesting for me to see how you automate the operations in your script
oorexx.jlf. It covers everything from how to check out, up to the rpm build.
A preliminary remark : given the experimental aspect of my sandbox, I had
in mind a "no install" delivery for preview, rather than a "real" install.
So I would be interested to know if you have specific reasons to make a rpm
(I'm just curious :-)
I have a question about this comment in your script :
*Patches install also trunk/samples/native.api; they do not install new
header files.*
Normally, I'm in sync with main/trunk, so it means that samples/native.api
are not part of the official delivery, and should be ? I did not take time
to verify... The files are listed below.
And which are these new header files not installed ?
I applied the patches and made a make install (I don't have rpmbuild).
Then, I made a diff between the previous tree file, and the new one. The
new files are listed below, and that brings some questions :-)
> ooRexx-jlf/bin/concurrency
> ooRexx-jlf/bin/concurrency/activity.cls
> ooRexx-jlf/bin/concurrency/coactivity.cls
> ooRexx-jlf/bin/extension
> ooRexx-jlf/bin/extension/array.cls
> ooRexx-jlf/bin/extension/doers.cls
> ooRexx-jlf/bin/extension/extensions.cls
> ooRexx-jlf/bin/extension/functionals.cls
> ooRexx-jlf/bin/pipeline
> ooRexx-jlf/bin/pipeline/pipe_extension.cls
> ooRexx-jlf/bin/profiling
> ooRexx-jlf/bin/profiling/profiling.cls
> ooRexx-jlf/bin/regex
> ooRexx-jlf/bin/regex/regex.cls
All the files above are more library files than binary files. I understand
that putting them in bin let find them automatically, because the PATH
includes the bin directory. But see below, there are also some library
files that you put under share/ooRexx.
Assuming we start thinking about a standard library for ooRexx, what should
be the file organization ? I did not take time to study Python and Ruby
libraries, there are probably some common practices.
> ooRexx-jlf/share/ooRexx/native.api
> ooRexx-jlf/share/ooRexx/native.api/call.example
> ooRexx-jlf/share/ooRexx/native.api/call.example/ReadMe.txt
> ooRexx-jlf/share/ooRexx/native.api/call.example/Makefile.linux
> ooRexx-jlf/share/ooRexx/native.api/call.example/Makefile.windows
> ooRexx-jlf/share/ooRexx/native.api/call.example/backward.fnc
> ooRexx-jlf/share/ooRexx/native.api/call.example/runRexxProgram.cpp
> ooRexx-jlf/share/ooRexx/native.api/call.example/stackOverflow.cpp
> ooRexx-jlf/share/ooRexx/native.api/call.example/HelloWorld.rex
> ooRexx-jlf/share/ooRexx/native.api/call.example/tooRecursiveTrapped.rex
> ooRexx-jlf/share/ooRexx/native.api/call.example/tooRecursiveUnhandled.rex
> ooRexx-jlf/share/ooRexx/native.api/ReadMe.txt
See my previous question about native api files.
> ooRexx-jlf/share/ooRexx/pipeline
> ooRexx-jlf/share/ooRexx/pipeline/pipe.rex
> ooRexx-jlf/share/ooRexx/pipeline/pipe_readme.txt
> ooRexx-jlf/share/ooRexx/rgf_util2
> ooRexx-jlf/share/ooRexx/rgf_util2/rgf_util2.rex
> ooRexx-jlf/share/ooRexx/rgf_util2/rgf_util2_wrappers.rex
Files above are library files. "share/ooRexx" seems the good place to
deliver them. I assume this directory is added to PATH by the installer ?
> ooRexx-jlf/share/ooRexx/_samples
> ooRexx-jlf/share/ooRexx/_samples/doers-benchmark.rex
> ooRexx-jlf/share/ooRexx/_samples/doers-info.rex
> ooRexx-jlf/share/ooRexx/_samples/doers-samples.rex
> ooRexx-jlf/share/ooRexx/_samples/doers-stress.rex
> ooRexx-jlf/share/ooRexx/_samples/functional-test.rex
> ooRexx-jlf/share/ooRexx/_samples/pipe_extension_test.rex
Files above are samples files. No remark, except maybe that we have some
sample files directly under "share/ooRexx". Maybe we need a proper
distinction between library files and samples files ?
> ooRexx-jlf/share/ooRexx/trace
> ooRexx-jlf/share/ooRexx/trace/tracer.rex
> ooRexx-jlf/share/ooRexx/oorexxshell.rex
Files above are utility scripts, so candidate to go in bin, unless there is
also a common practice (other than bin) to deliver utility scripts like
that ?
> ooRexx-jlf/share/ooRexx/readme.txt
Jean-Louis
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
