David,
Still have to go and make a detailed check that everything is correct, but
my first impressions are this is really great! We might want to consider
expanding this even further by making the class names and the method names
xrefs using the technique we're using for the inherited method
On 12/11/2013 6:23 PM, David Ashley wrote:
Yes, this looks good. BTW, I noticed the Array class is missing its
class methods, 'Of' and 'New'.
I finished replacing the class diagrams in collclasses.xml. Rexxref now
builds correctly. A new rexxref will be ready in the morning.
Please let me
Gil, just committed the fix for that a couple minutes ago. There are a few
other errors I found, mostly because the original image file was missing
some things. The other big error was Queue lost about half its methods.
Rick
On Thu, Dec 12, 2013 at 9:07 AM, Gil Barmwater
Ok, I've completed a complete review of this section and committed fixes
for a few problems (not all of which were with your update, so this was a
useful exercise!).
Rick
On Wed, Dec 11, 2013 at 6:23 PM, David Ashley w.david.ash...@gmail.comwrote:
I finished replacing the class diagrams in
Re: future update and correctness -
Could the production of the diagram be automated?
Isn't the information in the class diagram available by inspection
methods? If not, the meta-question is Shouldn't they be?
-Chip-
On 12/12/2013 06:51 Rick McGuire said:
Still have to go and make a
On Wed, Dec 11, 2013 at 11:47 PM, Mike Cowlishaw m...@speleotrove.comwrote:
That makes very good sense ...
How about creating a link on the desktop that links to the ooRexx menu
folder?
I tried that yesterday, it is relatively easy to add to the current
installer.
The last 'Finish' page
Sounds fine with me. I suggest opening an RFE for it so you have something
to add to the changes file.
Rick
On Thu, Dec 12, 2013 at 11:58 AM, Mark Miesfeld miesf...@gmail.com wrote:
On Wed, Dec 11, 2013 at 11:47 PM, Mike Cowlishaw m...@speleotrove.comwrote:
That makes very good sense ...
On Thu, Dec 12, 2013 at 9:05 AM, Rick McGuire object.r...@gmail.com wrote:
Sounds fine with me. I suggest opening an RFE for it so you have
something to add to the changes file.
Yes I was going to open an RFE. I didn't mention it because I was
practicing my Walter persona - being brief to
All -
I cannot believe I have been using ooRexx on Linux for about 10 years
and I just had something pointed to me by a user that I have never
noticed before.
When ooRexx creates a file on *nix that file is created with the
permissions -rw--- which means that only the owner can read and
Sort of thought that Linux users were like Windows users .. essentially a
single-user machine. So the whole issue is somewhat academic (as is perhaps
proven by the fact that it took ten years to notice).
The whole multi-user-on-a-single-PC approach of Linux and Windows is a bit
dated. VMWare
-11.06.00.00-20131212-43362.tmp,
O_RDWR|O_CREAT, 0600) =
4
You can see where the 0600 is used for to set the file permissions.
There are several options to fixing this. The easiest is just setting
the read bit for Group and Other. The correct method is to fetch the
user's umask and setting
While you argument is somewhat true, Linux is used as a server operating
system more that a single user computer. And this can cause problems
when ooRexx creates files to consumed by user other that the creator. It
is especially problematic when an ooRexx server process (like mod_rexx
for
is the strace
for the call which was caused by a lineout function call which opened a
new file.
open(/ibm/tci/data/lodb/requests/crackdispo-testlot-1234567-2013-12-12-11.06.00.00-20131212-43362.tmp,
O_RDWR|O_CREAT, 0600) =
4
You can see where the 0600 is used for to set the file permissions
On Thu, Dec 12, 2013 at 1:08 PM, Rick McGuire object.r...@gmail.com wrote:
I suspect we need to be doing the right fix rather than the easy fix.
I agree, the easy fix seems worse than the current behavior. What if the
user doesn't want others to be able to read the file. Better the user has
Sounds good to me too!
Oliver
_
From: Rick McGuire [mailto:object.r...@gmail.com]
Sent: 12 December 2013 18:05
To: Open Object Rexx Developer Mailing List
Subject: Re: [Oorexx-devel] ooRexx does nothing visible when installed.
Sounds fine with me. I suggest opening an RFE for it so
-20131212-43362.tmp,
O_RDWR|O_CREAT, 0600) =
4
You can see where the 0600 is used for to set the file permissions.
There are several options to fixing this. The easiest is just setting
the read bit for Group and Other. The correct method is to fetch the
user's umask and setting the bits based
is the strace
for the call which was caused by a lineout function call which opened a
new file.
open(/ibm/tci/data/lodb/requests/crackdispo-testlot-1234567-2013-12-12-11.06.00.00-20131212-43362.tmp,
O_RDWR|O_CREAT, 0600) =
4
You can see where the 0600 is used for to set the file permissions
All -
I finished replacing the class diagrams in fundclasses.xml and a new
rexxref should be available in the morning, provided any new patches do
not introduce problems.
David Ashley
--
Rapidly troubleshoot problems
Reviewed and few small corrections made.
Rick
On Thu, Dec 12, 2013 at 6:25 PM, David Ashley w.david.ash...@gmail.comwrote:
All -
I finished replacing the class diagrams in fundclasses.xml and a new
rexxref should be available in the morning, provided any new patches do
not introduce
I am out of the office until 16-12-2013.
For PPL issues: please contact Nico Vriend or for urgent matters Georges
Spittael
Note: This is an automated response to your message Oorexx-devel Digest,
Vol 91, Issue 28 sent on 12/12/2013 21:00:39.
This is the only notification you will receive
Hi,
Thanks! It passed on the validation and the packet was created with a
few other warnings (below); just enbled build of the 32 bits and
OpenSUSE´s factory package
Just to keep you informed there´s the last warnings from OpenSUSE´s
validation system:
RPMLINT report:
===
21 matches
Mail list logo
