I'd like to use ooRexx and ncurses to create a text-driven app for a
netbook that doesn't need an Xwindow system to be installed. Any
thoughts or tips on getting the code compiled would be appreciated.
Thx.
Les (Change Arabic to Roman to email me)
Thanks for the information Les. Unfortunately, I'm unable to access any
postings earlier than 10/15/09 for some reason...
Jeff
You should be able to see the thread here:
Rexx/Curses works fine with ooRexx, as long as you are using a version
of ooRexx before 4.0.
Rexx/Curses is written to work with multiple Rexx interpreters that
implement the Rexx SAA API.
ooRexx implemented a new object based API, but left the old SAA API in
ooRexx 4.0 so legacy applications would still work but changes were
made to the old API so that legacy applications do not work anymore :-
(
If you want to be able to use Rexx/Curses with ooRexx 4.0 then you
should be asking the ooRexx development team whether they intend
fixing the SAA API implementation so that legacy applications continue
to work.
If you want to use Rexx/Curses, then I'd suggest you use a Rexx
interpreter that DOES support the SAA API, like Regina or REXX/imc.
Cheers, Mark
> ooRexx implemented a new object based API, but left the old SAA API in
> ooRexx 4.0 so legacy applications would still work but changes were
> made to the old API so that legacy applications do not work anymore :-
> Cheers, Mark
I just today read Rexref,
and
::requires ... LIBRARAY REGISTERED
suggests, the old API wil still work!?
Is this so or not ((example in the doc is rexxsql).
Wolfgang
Hi Wolfgang,
Having spent a few days trying to change the code I use for building one
of my applications that use the SAA API to work with ooRexx 4.0 (and not
break the use of other interpreters) and still not having any success I'm
very confident that the ooRexx 4.0 SAA API is broken and whatever might
be in the ooRexx 4.0 documentation is incorrect.
Cheers, Mark
Cheers.
I guess that this is why Blair Thompson's X editor does not work with ooRexx
4.0 (at least, the version of X that I am using). X uses Rexx for its
user-written macros.
I uninstalled ooRexx 4.0 and re-installed ooRexx 3.2. Sigh.
-- from CyberSimian in the UK
If you've suddenly had to add a (new) line to your code, if possible,
to be able to use some (old) API, that already means compatability is
lost due to another design mistake. And if the example indeed is some
'RexxSQL', then what part of '::requires WHATEVER' is compatible with
(old) Rexx? It ain't OrexxSQL.
---
Then it isn't Ansi or SAA Rexx.
I think, this is a mistake of the oorexx team in their newfound
fondness
of C++! (And: C++ by itself does everything to enable C-compatibility
-
but with some difficulties.)
It should be a high-priority (higher f.e. than 64-bit for all
platforms) task of the team,
to correct this,
if they don't want to make oorexx a new and incompatible language to
rexx.
(I will look into the sources to prevent this;
I use oorexx and regina (after OS/2) for different tasks, where there
are strengths
(OLE, clipbboard) <-> rxsock etc.)
Wolfgang
>
> Then it isn't Ansi or SAA Rexx.
> I think, this is a mistake of the oorexx team in their newfound fondness
> of C++! (And: C++ by itself does everything to enable C-compatibility -
> but with some difficulties.)
> It should be a high-priority (higher f.e. than 64-bit for all platforms)
> task of the team,
> to correct this,
> if they don't want to make oorexx a new and incompatible language to
> rexx.
>
> (I will look into the sources to prevent this; I use oorexx and regina
> (after OS/2) for different tasks, where there are strengths
> (OLE, clipbboard) <-> rxsock etc.)
>
> Wolfgang
Good luck with getting any changes accepted. Please see the comments in
the bug report I submitted in May when I first found this issue.
Bug number 2794834.
https://sourceforge.net/tracker/?
func=detail&aid=2794834&group_id=119701&atid=684730
I think you do not understand the maining of: RexxLA is an independent,
non-profit organization dedicated to promoting the use and understanding
of the Rexx programming language
> I think, this is a mistake
I'm sure this is a mistake. ooRexx is the worst thing that happened to
Rexx.
> It should be a high-priority (higher f.e. than 64-bit for all
> platforms) task of the team, to correct this
They don't care. Please read their mission statement above.
> if they don't want to make oorexx a new and incompatible language
> to rexx.
"oorexx" isn't a language. Just like "Borland C" isn't a language.
ORexx perhaps is a language, or some language derivate.
> I will look into the sources to prevent this
Save the 3.2.0-one? The last one not broken beyond reasonable repair,
and there'll be nothing in who-cares-4.0.0 you cannot live without.
> I use oorexx and regina
Regina is probably the best Rexx interpreter ever, but RexxLA's ooRexx
toy basicly stopped that. I really fear you don't understand the RexxLA
goals, as quoted above. Who needs RexxSQL? Don't expect the RexxLA to
promote SQL! I never ever saw a real external, third-party ORexx app,
so I'ld really need to run that as fast as possible. I'm sure you'll
understand! ;-)
---
I have ported programs to 64-bit on multiple platforms myself.
That windows is weird (even this may be done with ###), is no excuse
to
no longer have API stability (see f.e. openssl or Curl)(nobody awaits
ABI stability
while AIX shows, even this is possible)
Wolfgang
I care - doesn't mean I can fix this one.
Jon - RexxLA member, ooRexx project committer, dedicated Rexx\SQL user
> ooRexx is the worst thing that happened to Rexx.
Could you elaborate a little, please?
(As a long-term user of Rexx on IBM mainframes decades ago, I was
delighted to find a version (ooRexx) that I could install under Linux.
It works fine, though my usage is quite low.)
--
/\/\aurice
(Retired in Surrey, UK) Registered Linux User #487649
http://www.maurice99.ukfsn.org
Linux Mandriva 2009.1 32-bit PowerPack (i686 kernel)
(Replace "nomail.afraid" by "bcs" to reply by email)
So, now, it's no more a matter of convenience (like easyness of using
the windows clipboard)
but necessity to use the one or other - and that should not happen.
(Btw. - I sent some bugreports for regutils and got no reaction -
the SysStem... routines all destroy a. = 0).
But: to be able to use f.e. Rexx/SQL or other utilities -
(what is the status of rexxtrans in all this?)
is too important for me.
Wolfgang
(btw. has anybody tried to use ppwizzard with oorexx 4.0?
the author might have s.th. to say)
Hi Wolfgang, Maurice,
maybe it would help make things clearer If I posted this piece I wrote
yesterday, but was unsure whether to post or not (because I don't want
to get flamed)
On Thu, 05 Nov 2009 21:30:24 +0200, ML wrote:
> ooRexx is the worst thing that happened to Rexx.
Could you elaborate a little, please?
Ok, ML doesn’t seem in a hurry to answer this, so I’ll try.
This is not to say that I speak for him, I don’t even know who he is.
Nor do I agree with his opinions that ooRexx is the worst thing that
happened to Rexx or that ooRexx is a toy or indeed his (ironic?)
assertion that RexxLA doesn’t care about Rexx.
I’m also not the best person to tackle what is quite a complicated
technical issue because I’m not a C or C++ programmer which is where
the heart of this difficulty lies. Maybe some of what I present below
will be factually inaccurate or use the wrong terminology, but
hopefully it will serve to get the ball rolling towards a more correct
understanding of a knotty issue.
There are several Rexx interpreters out there, and Mark Hessling has
developed and been custodian of interpreters and tools that have been
and are important to the Rexx community and he has done work to make
them available across interpreters.
There are several tools, and this thread is about ncurses in
particular, which I am not familiar with, but I have been following
what happens to Rexx\SQL with ooRexx with a great deal of interest.
One of the goals of the ooRexx 4.0 release was to get ooRexx going on
64 bit platforms. In pursuance of this goal a decision was made to
make some changes to the headers used in the API. Previously the
headers made use of a type called ULONG. In the 4.0 release those
headers are now type size_t. On a 32 bit system, both these types
resolve to an unsigned 32 bit number.
Because of this, the binaries for Mark’s utilities will still work
with ooRexx 4.0 in a 32 bit environment, but Mark cannot compile his
code unchanged from source.
I believe that a member of the ooRexx development team has managed to
get the Rexx\SQL source to compile against the ooRexx 4.0 headers for
use on 32 bit windows, by amongst other things omitting the rexxTrans
include – but to pursue this route would mean maintaining separate
source for ooRexx 4.0 onwards from those for the other Rexx
interpreters that Mark supports which he and other suppliers of rexx
tools may or may not want to do.
As I understand it, Rexx\SQL can’t make use of a 64 bit platform at
present.
Also as I understand it Rexx\Trans allows one to use extension
packages with different interpreters on the same machine at the same
time. It has become something of a defacto standard, but probably
cannot accommodate the changes in the ooRexx v4.0 headers due to loss
of binary compatability.
The Rexx language is enshrined in an ANSI standard, and that helps to
maintain compatibility across interpreters and tools and everyone
agrees that is a good thing. The headers in question were developed
when Rexx was ported to 16 bit OS/2 in 1988 and are not covered by the
ANSI standard. That isn’t to say that it is not desirable to maintain
portability where one can, but I am assured that those headers won’t
work on a 64 bit platform.
I had to look up what SAA (Systems Application Architecture) was and
cannot comment on to what extent ooRexx 4.0 still complies to that
standard, or even whether it should – ML seems to believe that it
should and that it doesn’t.
So, we now have a powerful Object Oriented Rexx interpreter that will
utilise a 64 bit platform, but we have some compatibility issues in
it’s wake.
I hope that helps clarify things a little.
Jon
sorry,
Jon
> ML doesnļæ½t seem in a hurry to answer this, so Iļæ½ll try.
Many thanks, Jon! Much appreciated,,,
--
/\/\aurice
(Retired in Surrey, UK)