On Mon, Feb 20, 2012 at 10:18 PM, Sahananda (Jon) Wolfers
sahana...@windhorse.biz wrote:
Just a couple of questions.
1) The Changes list here appears to be empty. Does it exist somewhere else.
It is empty, it doesn't exist somewhere else. It will be filled in shortly.
2) The release
Hi Mark,
I installed the 32 bit fedora version on Centos - it complains about
libstdc++.so.6: version 'GLIBCXX_3.4.15' not found (required by
/usr/lib/ooRexx/librexxapi.so.4), I installed glibc separately with yum but
that did not help.
The Windows 7 install is plagued by extreme nagging
The RXOFNC and RXEXF exits are the oo exits for which the PARM-block defines
RexxObjectPtr et.al.
types.
As I am getting a very strange behaviour in both exits when processing the
argument array it may be
the case that I am not iterating correctly over the array, so here is first the
The classic Rexx exit RXFNC will raise a Rexx condition, if the handler
either sets the rxfferr
(invaliid call to routine) or the rxffnfnd (function not found) flag and
returns with
RXEXIT_HANDLED.
Doing the same in the ooRexx-supported RXOFNC/RXEXF handlers does not raise
the Rexx condition
Hi René
On Tue, Feb 21, 2012 at 11:34 AM, René Jansen rvjan...@xs4all.nl wrote:
I installed the 32 bit fedora version on Centos - it complains about
libstdc++.so.6: version 'GLIBCXX_3.4.15' not found (required by
/usr/lib/ooRexx/librexxapi.so.4), I installed glibc separately with yum but
On 21.02.2012 20:48, Rony G. Flatscher wrote:
The classic Rexx exit RXFNC will raise a Rexx condition, if the handler
either sets the rxfferr
(invaliid call to routine) or the rxffnfnd (function not found) flag and
returns with
RXEXIT_HANDLED.
Doing the same in the ooRexx-supported
On 21.02.2012 21:05, Mark Miesfeld wrote:
... cut ...
A certificate for RexxLA would be an ideal solution. The certificate
would work for both products and would work for both a NSIS installer
or a MSI installer, and I'm pretty sure for any product that produces
a Windows installation
I don't see anthing obviously wrong here. Provide a sample program so
I can recreate this, and I'll take a look at it.
Rick
On Tue, Feb 21, 2012 at 2:42 PM, Rony G. Flatscher
rony.flatsc...@wu-wien.ac.at wrote:
The RXOFNC and RXEXF exits are the oo exits for which the PARM-block
defines
Hi Mark
thanks for your quick answer.
On 21 feb. 2012, at 21:05, Mark Miesfeld wrote:
We have found that on many of the Linux versions, the installer
package needs to be built on the same Linux as it is to be installed
on. This is true on Debian versions, SuSE versions, etc. I.e., a
I take that back, I do see something obviously wrong. Rexx arrays are
1-based, not 0-based, so your put call needs to be specifying an index
of i+1.
Rick
On Tue, Feb 21, 2012 at 3:37 PM, Rick McGuire object.r...@gmail.com wrote:
I don't see anthing obviously wrong here. Provide a sample
On Tue, Feb 21, 2012 at 12:39 PM, René Jansen rvjan...@xs4all.nl wrote:
... Still I do not like all the
implications of this - this is a serious programming product and I am
seriously offended by the tone of some of these messages. So we should do
something about it.
Looking into it a
On 21.02.2012 21:49, Rick McGuire wrote:
I take that back, I do see something obviously wrong. Rexx arrays are
1-based, not 0-based, so your put call needs to be specifying an index
of i+1.
Aaargh, thank you *very* much, indeed !
---rony
P.S.: I have been chasing that down for hours and
In the AOO (Apache OpenOffice, an incubator project) developer group there was
some discussion about
documentation and help editing with pointers to DITA
http://dita.xml.org/standard and a pointer to
a free XML editor that is able to process all kinds of XML DTD/XSD, including
Bookmaster was
Hi David,
When I go to build the oodguide PDF file, I get a message saying:
jade:Chapter06.xml:1:0:E: character data is not allowed here
I can't figure out what the problem is there.
1.) there is no character at line 1, character 0 - it is 1 character
before the file starts. ;-)
2.) the
14 matches
Mail list logo
