Not CUA, but GTK+ and QT might be reasonable choices.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Assembler List [ASSEMBLER-LIST@LISTSERV.UGA.EDU] on behalf
of Charles Mills [charl...@mcn.org]
Sent: Thursday, November
Musing further on this, I would think the C++ dialect itself would not be a
problem. What would be a problem -- merely a big problem, or a huge problem
I do not know -- would be the screen GUI library. I would guess Visual Age
had its own. CUA? Visual Studio has MS Foundation Classes. I don't know
I hear you.
I suspect for an enthusiast with time on their hands a port from VisualAge
C++ to gcc or Visual Studio C++ would not be an impossible leap. But
obviously, the legal rights question comes ahead of the porting question.
Charles
-Original Message-
From: IBM Mainframe Assembler
Charles writes:
> I know this is above your pay grade but why not open source it? I'll bet
> there are a half a dozen folks that would love to get it working on current
> Windows and perhaps Linux too.
In the past, other IBM internal teams have been given a copy of
ASMPUT with a view to
On Nov 18, 2021, at 08:20:50, Charles Mills wrote:
>
> I know this is above your pay grade but why not open source it? I'll bet
> there are a half a dozen folks that would love to get it working on current
> Windows and perhaps Linux too.
>
What source language? If ASMPUT originated on OS/2
I know this is above your pay grade but why not open source it? I'll bet
there are a half a dozen folks that would love to get it working on current
Windows and perhaps Linux too.
Charles
-Original Message-
From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU]
On
Thank you for the explanation! I'll forgo the use of ASMPUT and pursue a
different solution for the issue.
Respectfully,
*Mark Hammack*
Senior z/OS Developer
Systemware, Inc.
mark.hamm...@gmail.com
214-478-0955 (c)
On Thu, Nov 18, 2021 at 3:49 AM Jonathan Scott
wrote:
> Mark Hammack wrote:
>
Ref: Your note of Wed, 17 Nov 2021 18:09:47 +
gil writes:
>Also, decades ago, I found that (something like):
>PSWMAP DSECT
> ...
> USING PSWMAP-SVCOPSW,R0
>
>quietly behaved as if I had coded:
> USING PSWMAP,R0
>
>Experts conceded that the behavior is indefensible
Mark Hammack wrote:
> I just downloaded the "latest" version of ASMPUT from z/OS 2.3 and have
> some questions.
ASMPUT has not been supported at all since 2017, as announced in
APAR PI81310. It was probably last built (or possibly just
patched) in 2004, for HLASM 1.4. The last functional update
