They say that the memory is the second thing to go; I don't remember the first
thing.
Given that Mike Cowlishaw was involved in developing ANSI X3.274-1996, I'm
pretty sure that he would claim that to be the standard Rexx language, just as
I'm pretty sure that John Backus would consider
People seem to identify as "modern" what they learned at University.
I didn't attend a University, at the time it was a Polytechnic. We learned
Fortran on an ICL machine (no idea what model).
I thought programming was not for me based on what we were taught, rather
for the next man.
Reminds me
Can't resist:
The Call of the West
Eccles: The wagon train with your wife on board has been attacked by the
Indians!
Captain: My wife? Is she safe?
Eccles: Yeah.
Captain: I never did like them Indians.
Lt. Hern: Did they follow you?
Eccles: Yeah. They were shooting at me all the time. But I just
On Fri, Apr 24, 2020 at 7:12 PM Seymour J Metz wrote:
> Hey, it's not politically correct to point out how old C is.
>
I always thought it was named "C" because that would have been the grade a
student would have gotten if he/she had designed it in a modern computer
science class.
>
>
> --
>
HLASM in 1980? Not before June 1992. I assume that you were using XF and H,
possibly with the SLAC mods on the latter (thank you, Greg and John.)
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List
OREXX in OS/2:
Sun 4-26-20 10:16:16Sun 4-26-20 10:16:16{1}[h:\] H:\$REXX\trynot.cmd
Trying \ 5C
\ recognized
Trying ¬ AA
¬ recognized
Trying ¼ AC
6 *-* compare = a ¼
6 *-* interpret 'compare = a' Not'= b'
REX0013E: Error 13 running H:\$REXX\TRYNOT.CMD line 6: Invalid character in
On Sun, 26 Apr 2020 07:39:27 +, Seymour J Metz wrote:
>They say that the memory is the second thing to go; I don't remember the first
>thing.
>
>Given that Mike Cowlishaw was involved in developing ANSI X3.274-1996, I'm
>pretty sure that he would claim that to be the standard Rexx
I took my first C course in 1980. The text was the original *The C
programming Language* by Kerrigan and Richie, which I still have on my
shelf, The text is copyright 1978. That's 42 years ago. I was an IBM HL
Assembler programmer at the time. BTW ... we still were using IFOX00 at the
time as
I would like to see an examples of an IPCS RUNARRAY command where the EXEC
clause display storage using a pointer as a displacement off of X.
So far I have not been able to make it work.
--
Binyamin Dissen
http://www.dissensoftware.com
Director, Dissen Software, Bar & Grill - Israel
Should
HI
I am looking in the XL C docs lang reference user guide programming guide
For the length of the following data types
Short , int long and I cannot seem to find it
frustrated
I coded a program
Int len;
Unsigned short shortype;
I would have assigned it an E at the time; I was appalled. C++ cleans up some
but not all of the warts, and a lot of the warts in C++ are there only for
compatibility.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe
The is a PL/AS and a PL/X, both ultimately derived from BSL (the languages, not
the code base.) AFAIK there is no PL/ASX.
Does anybody remember the full family tree for BSL, PL/8 (or should that be
PL.8?) et al?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
On 4/25/20 3:51 PM, Paul Gilmartin wrote:
> I did not copy-and-paste; I downloaded the attachment,
> which appears to be UTF-8.
>
> For Regina, Regina.pdf says: 3.1.1.1 Negators
> ... Regina supports the following characters as negators:
> ...
> ¬ Logical Not
> Copy-and-paste from the
On 4/25/20 2:56 PM, Rob Schramm wrote:
I wonder when someone is going to write a javac that actually produces C
code for the platform. Kind of like PL/asx ( I may have this acro wrong )
Modern Java VMs are about as efficient as can be, given the object model.
That's why the notion of Java ->
On 2020-04-26, at 08:41:24, Jack J. Woehr wrote:
>
> On 4/25/20 2:56 PM, Rob Schramm wrote:
>> I wonder when someone is going to write a javac that actually produces C
>> code for the platform. Kind of like PL/asx ( I may have this acro wrong )
>
> Modern Java VMs are about as efficient as can
Don't allow extraneous factors (such as optimization or argument promotions)
to obfuscate the information you want. If you want the sizes of the types,
print the sizes of the types.
#include
int main(void)
{
printf("%zd %zd %zd", sizeof(short), sizeof(int), sizeof(long));
return
Mike Cowlishaw created the Rexx language
https://en.wikipedia.org/wiki/Mike_Cowlishaw
On 26/04/2020 15:48, Paul Gilmartin wrote:
> On Sun, 26 Apr 2020 07:39:27 +, Seymour J Metz wrote:
>
>> They say that the memory is the second thing to go; I don't remember the
>> first thing.
>>
>>
+1
Or RTFKC:
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1
.cbclx01/zos_supporting_ansi_iso_standards.htm
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of retired mainframer
Sent: Sunday, April
On Sun, 26 Apr 2020 13:38:49 -0400, Joseph Reichman wrote:
>Tried that great idea however I think you helped me uncover a bug in the
>compiler
>So it seems that a short is 2 bytes look below
>
>However when I passed reclen as a parameter it was by value not by address
>guess what the compiler
We had a similar package of SP (structured programming) macros in Germany,
very powerful (IF...THEN...ELSE...EIF, LOOP WHILE/UNTIL...ELOOP etc.).
Most interesting: there were always multiple conditions on IF and LOOP,
separated by asterisks, so
IF...THEN(1)...THEN(2)...THEN(3)...ELSE...EIF in
The question and the subject do not seem to go together.
Shorts are 16 bits; long and long ints are 32 bits on most modern C
compilers.
As @John says, statements that "don't matter" go away. If you set len and
then do not use it, the compiler is free to disregard the setting.
Try the volatile
Some of the portability issues have (mostly) gone away because of changes in
the language and the demise of, e.g., 36-bit computers as a significant
presence in the market place, and some you have to handle on an ad hoc basis
with #if and #ifdef in your header files.
--
Shmuel (Seymour J.)
I was doing an internship in the Chicago area during the summer of
1984. They were using an assembler with IF macros.
On Sun, Apr 26, 2020 at 2:11 PM Seymour J Metz wrote:
>
> HLASM in 1980? Not before June 1992. I assume that you were using XF and H,
> possibly with the SLAC mods on the
Those macros were not part of the assembler. As I recall there was a popular
macro package called CONCEPT 101 (sp?) floating around, and another package
called PROC, but they didn't come from IBM.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
On Sun, Apr 26, 2020 at 8:58 AM Joseph Reichman
wrote:
> HI
>
>I am looking in the XL C docs lang reference user guide programming
> guide
>
> For the length of the following data types
>
>
>
> Short , int long and I cannot seem to find it
>
>
>
> frustrated
>
>
>
>
Tried that great idea however I think you helped me uncover a bug in the
compiler
So it seems that a short is 2 bytes look below
However when I passed reclen as a parameter it was by value not by address
guess what the compiler did
L R14,@...RECLEN
ST R14,232(R13)
I would
I thought the macros were part of CONCEPT 14? I do remember working on IBM
3684 point of sale systems between 1982 and 1986. They were programmed
using an Asembler like language called SPSS II, it had IF THEN ELSE and
other macros.
On Mon, Apr 27, 2020, 03:36 Seymour J Metz wrote:
> Those
thanks
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Charles Mills
Sent: Sunday, April 26, 2020 3:59 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: XL C\C ++ sizeof of datatypes
+1
Or RTFKC:
SPPS was the language. Google can't find it but it's embedded in the 3651
store controller manuals.
On Mon, Apr 27, 2020, 06:01 Wayne Bickerdike wrote:
> I thought the macros were part of CONCEPT 14? I do remember working on IBM
> 3684 point of sale systems between 1982 and 1986. They were
Wayne,
I didn’t learn C or SPSS for example, learned the IBM Lang’s, Assembler,
Cobol, PL/1 and FORTRAN IV and of course rexx and various other command
list languages on VM and MVS. But your reference to IBM 3600 brought my
past life as a VSE Sysprog we wrote 3600 replacement programs for 8100s .
> I thought the macros were part of CONCEPT 14?
CONCEPT 14 (http://skycoast.us/pscott/software/mvs/c14/c14-.html) could be
what I was thinking of. It's the basis for the macro package in the HLASM
Toolkit.
The macro package I actually used was called PROC.
>
> Mike Cowlishaw created the Rexx language
Yes, and if you look at the article you linked to, you will see "He has
contributed to and/or edited various computing standards, including ISO (SGML,
COBOL, C, C++), BSI (SGML, C), ANSI (REXX), IETF (HTTP 1.0/RFC 1945), W3C (XML
Schema), ECMA
Is it failing even when everything is in the same address space?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Binyamin Dissen [bdis...@dissensoftware.com]
Sent:
On Sun, 26 Apr 2020 12:58:57 -0700, Charles Mills wrote:
>+1
>
>Or RTFKC:
>https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.cbclx01/zos_supporting_ansi_iso_standards.htm
>
Where I read:
Equivalent type of char: signed char, unsigned char, or user-defined:
The
In article <006301d61bd2$bf391680$3dab4380$@gmail.com> you wrote:
> HI
>I am looking in the XL C docs lang reference user guide programming guide
> For the length of the following data types
> Short , int long and I cannot seem to find it
> frustrated
> I
Without testing, I think that a signed char argument satisfies and unsigned
char formal parameter, but that char does not satisfy unsigned char *.
There is some C messiness around char signage. I think on most platforms char
is kind of the same as signed char, but not exactly the same. On Z a
Actually, on the 3600 you could select whether indexing was 1s' complement or
2' complement. I had lust in my heart for that machine and its big brother, the
3800.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion
First of all, char in C is a subtype of int,
which means that you can do normal arithmetic operations to chars
and that chars are allowed in int expressions without special action
needed.
for example:
char c;
c = 'A' + 1; /* c will be 'B' */
c = c - 'A' + 'a'; /* c will now be 'b' - lower
On Mon, 27 Apr 2020 03:49:00 +0200, Bernd Oppolzer wrote:
>First of all, char in C is a subtype of int,
>which means that you can do normal arithmetic operations to chars
>and that chars are allowed in int expressions without special action
>needed.
>
>for example:
>
>char c;
>
>c = 'A' + 1; /*
Seymour,
The assembler was SPPS. Too close to the stats package name SPSS.
I was working at a DOS/VSE shop in England in 1983 and they had COBOL and
SPPS on their IBM cash registers.
I had neither mainframe COBOL nor SPPS skills but I'd written a whole bunch
of Microfocus COBOL on CP/M micros.
SPPS reminds of a little war story.
The garment retailer had a ticketing system whereby we printed sticky
labels, numbered in 100 increments. That's what the analyst specified.
These labels were quite expensive compared to line printer paper. They were
printed on the 1403 or whatever.
We ran a
The structured programming macros originated from IBM Federal Systems
Division and were called "Concept 14", freely available at the time. Many
variants were created in subsequent years, both within IBM and in the
mainframe open source community of the 1970's. IBM going to OCO impacted
their
Am 27.04.2020 um 04:21 schrieb Paul Gilmartin:
On Mon, 27 Apr 2020 03:49:00 +0200, Bernd Oppolzer wrote:
First of all, char in C is a subtype of int,
which means that you can do normal arithmetic operations to chars
and that chars are allowed in int expressions without special action
needed.
K did not require char to be at least 8 bits, but ANSI did.
I wonder what C did on a ones' complement machine if a string contained a -0
character?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List
I would like to add:
as explained, the types integer and char are incompatibel in Pascal.
Furthermore, char in Pascal is NOT a computational type; you cannot do
arithmetic with chars, and there is no sign with chars (much the same as
in PL/1,
for example). To do arithmetic with chars, you need
On Mon, 27 Apr 2020 04:23:49 +0200, Bernd Oppolzer wrote:
>I would like to add:
>
>as explained, the types integer and char are incompatibel in Pascal.
>Furthermore, char in Pascal is NOT a computational type; you cannot do
>arithmetic with chars, and there is no sign with chars (much the same as
On Mon, 27 Apr 2020 03:35:46 +, Seymour J Metz wrote:
>K did not require char to be at least 8 bits, but ANSI did.
>
>I wonder what C did on a ones' complement machine if a string contained a -0
>character?
>
POSIX specifies that the component characters should be compared
as if unsigned.
47 matches
Mail list logo
