:16 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Stop the ragging on COBOL please [was: RE: ASM call by value]
On Wed, 29 Mar 2023 at 11:20, Seymour J Metz wrote:
> "You can write FORTRAN in any language."
>
> Too be fair, much of what I take for granted in PL/I
: ASM call by value]
On Wed, 29 Mar 2023 14:16:56 +, Robert Prins wrote:
>> w..., and IBM rejected the original SHARE
>> requirement for a CASE statement.
>
>But the SELECT statement that they added (before my time) later beats the
>crap out of CASE in C & Pasca
I'm going to disagree only in a tiny and technical way: ITERATE forces more
discipline, but what that means is not that GOTO is less disciplined but that
GOTO ~allows~ less discipline. Back in my COBOL days I maintained that not all
GOTOs are evil; these three are just fine:
GOTO
inframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
> Paul Gilmartin [042bfe9c879d-dmarc-requ...@listserv.ua.edu]
> Sent: Wednesday, March 29, 2023 9:29 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Stop the ragging on COBOL please [was: RE: ASM call by value]
>
>
IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Stop the ragging on COBOL please [was: RE: ASM call by value]
On Wed, 29 Mar 2023 08:13:11 -0500, Joe Monk wrote:
>"Too many languages lack ELSEIF and strong closure. Fie on
>the danglig ELSE!"
>
>Now you know why COBOL programmers always i
On Wed, 29 Mar 2023 09:38:50 -0400, Bob Bridges wrote:
>I suppose so, but I always use SELECT, never ELSEIF. I think it's because
>with ELSEIF I feel compelled to indent each clause as if it were an "ELSE IF",
>
Sounds like a personal problem to me.
>and I abominate those long increasingly
I saw top down and bottom up structured code ideas. And somewhere
in there was Yourdon(?) structured "method". Meanwhile I was
mostly doing ALC in those days, unless I was needed to work on
applications under CICS, then it was COBOL.
Problem was, for CICS, straight line code was best and if
My degree is in Accounting, but I discovered computer programming during the
course of my studies and was thoroughly hooked; I went straight into
applications development after graduation. More than one prospective
employer looked at me with stars in their eyes saying "Oh, at last, a
programmer
>The source was unreadable because of the amount and size of copybooks.
>When compiled, the listing was so big that it was near impossible to
follow.
>Needless to say, the variable and paragraph names didn't help too much.
>Have you ever tried reading a DMS for CICS (again, 40 years ago)
Nah, there are no more COBOL programmers; their brains all rotted.
---
Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313
/* America is at that awkward stage. It's too late to work within the system,
but too early to shoot the bastards. -Claire Wolfe, _101 Things to Do 'Til the
I suppose so, but I always use SELECT, never ELSEIF. I think it's because with
ELSEIF I feel compelled to indent each clause as if it were an "ELSE IF", and I
abominate those long increasingly indented constructions:
if expr1 then stm1
else if expr2 then stm2
else if expr3 then do
On Wed, 29 Mar 2023 08:13:11 -0500, Joe Monk wrote:
>"Too many languages lack ELSEIF and strong closure. Fie on
>the danglig ELSE!"
>
>Now you know why COBOL programmers always indented their code ... it helps
>
Past tense? No longer?
>line up the IF...ELSE structure. That was of course before
And this is the reason I think complaints about Python's syntactic
indentation miss the point: it's simply the language using what you should
be doing anyway.
On Wed, Mar 29, 2023 at 8:13 AM Joe Monk wrote:
> "Too many languages lack ELSEIF and strong closure. Fie on
> the danglig ELSE!"
>
>
"Too many languages lack ELSEIF and strong closure. Fie on
the danglig ELSE!"
Now you know why COBOL programmers always indented their code ... it helps
line up the IF...ELSE structure. That was of course before VS COBOL II
(Cobol '85).
Joe
On Wed, Mar 29, 2023 at 8:01 AM Paul Gilmartin <
On Wed, 29 Mar 2023 14:16:56 +, Robert Prins wrote:
>> w..., and IBM rejected the original SHARE
>> requirement for a CASE statement.
>
>But the SELECT statement that they added (before my time) later beats the
>crap out of CASE in C & Pascal.
>
Pascal CASE may have a performance
On Wed, 29 Mar 2023 at 11:20, Seymour J Metz wrote:
> "You can write FORTRAN in any language."
>
> Too be fair, much of what I take for granted in PL/I control structures
> was not in the original version, and IBM rejected the original SHARE
> requirement for a CASE statement.
>
But the SELECT
du/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Wayne Bickerdike [wayn...@gmail.com]
Sent: Wednesday, March 29, 2023 3:38 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Stop the ragging on COBOL please [was: RE: ASM call by value]
Regardi
Regarding Michael Jackson structured programming.
My first role at ICI was applications programmer. My Senior programmer gave
me three program specs that were training specs. The specs came with
flowcharts. I duly programmed them in PL/I replete with IF THEN GOTO ELSE
GOTO statements. Not a trace
On 28/3/23 13:26, Tony Harminc wrote:
I use programming languages that I don't like all the time. C, in
particular, I dislike a lot. That doesn't mean they're not useful.
Whew! And I thought you were a C fanatic. Thanks for disabusing me of that.
Ha! I don't develop emotional attachments to
On 28/3/23 13:56, Wayne Bickerdike wrote:
During my early training we were sent to learn Michael Jackson structured
programming.
I had a few brief years as an applications programmer back in the early
90s. I came from operations so I had to take the IBM aptitude test. The
interviewer held
It certainly does! Lots of applications developers hate that, but it always
seemed to me that it’s a necessary part of making usable code. If my users
never talked to me ("could you add a command arg that sorts the output this way
instead of that?"), I'd suspect - actually I'd be sure - that
the ragging on COBOL please [was: RE: ASM call by value]
I just wasn't that devious, but yeah, happens in real shops more
than one cares to admit.
Steve Thompson
On 3/28/2023 6:20 PM, Charles Mills wrote:
> Ha! I always said if I ever taught programming -- I never have -- I was going
>
I just wasn't that devious, but yeah, happens in real shops more
than one cares to admit.
Steve Thompson
On 3/28/2023 6:20 PM, Charles Mills wrote:
Ha! I always said if I ever taught programming -- I never have -- I was going
to do that -- swap code between students.
The other thing I was
Ha! I always said if I ever taught programming -- I never have -- I was going
to do that -- swap code between students.
The other thing I was going to do in the same vein was give a programming
assignment -- perhaps with a fairly tight deadline -- and halfway through say
"oh, wait, the specs
Very good method ... I was teaching programming during my career, much
the same as you did,
but I never did it like that. But I also encouraged the students to
discuss their solutions with me
and with other students and required that there be comments and
meaningful variable names etc.
IMO,
In an effort to keep people from writing difficult to impossible
to maintain code, while I was teaching COBOL, I warned the
students that I would be picking a programming lesson, where once
it was completed, everyone would have to swap card decks and then
have to add the next lesson's function
PL/I (or actually PL/C) was the first language I was exposed to, also - took a
class in college while getting my Accounting degree - and I still think it's
wonderful. A classmate was interviewing me for a job with his employer a few
years later and asked me what I thought to be the principle
With the clever use of GOTOs and the use of different variables with
strange names
for the same purpose, you can even turn a less than 1000 lines COBOL
program completely unreadable.
I see such programs almost every day.
The biggest obstacle for keeping large COBOL programs maintainable is
Ok, to be fair I tnd to abbrvt evrthg I can and use two- and thr-chr var
nams. I couldn't do that if I were still writing application programs for
my employer. Instead I write tools, utilities and commands that anyone can
use but no one bothers to maintain. I try to be careful to use a
warbrick
> Sent: Tuesday, March 28, 2023 12:52 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: ASM call by value
>
> So that didn't work. But after a lot of fiddling about, here's what works
> for me. I LE enabled it so it will be reentrant.
>
> ISCICS# CEEENTRY M
Another typo, of course.
=X'000100030003' should be =X'000100020003'
From: IBM Mainframe Discussion List on behalf of
Frank Swarbrick
Sent: Tuesday, March 28, 2023 12:52 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ASM call by value
So
Mainframe Discussion List on behalf of
Frank Swarbrick
Sent: Monday, March 27, 2023 11:49 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ASM call by value
So it looks like all I need is the following:
CALL @@GETCB,(3)
which should call the @@GETCB function passing integer 3 by value, returning 0
o
but this is an IBM product.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Thomas Kern
Sent: Tuesday, March 28, 2023 10:01 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Stop the ragging on COBOL please [was: RE: ASM call by value]
I haven't seen the inside of Waterloo
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Stop the ragging on COBOL please [was: RE: ASM call by value]
On 28/03/2023 9:34 pm, Seymour J Metz wrote:
> I once found myself defending the common idiom
>
> for (;;) {
>foo;
> }
>
> as a perfectly clear DO F
...@listserv.ua.edu]
Sent: Tuesday, March 28, 2023 11:01 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Stop the ragging on COBOL please [was: RE: ASM call by value]
I haven't seen the inside of Waterloo Script macros for al LONG time. It
will take me a while to get back into reading/debugging this just like
, 2023 11:15 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Stop the ragging on COBOL please [was: RE: ASM call by value]
You're close but this is an IBM product.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Thomas Kern
Sent: Tuesday, March 28, 2023 10:01 AM
To: IBM
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Schmitt, Michael [michael.schm...@dxc.com]
Sent: Tuesday, March 28, 2023 10:40 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Stop the ragging on COBOL please [was: RE: ASM call by value]
Yeah, but you can come back
You're close but this is an IBM product.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Thomas Kern
Sent: Tuesday, March 28, 2023 10:01 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Stop the ragging on COBOL please [was: RE: ASM call by value]
I haven't seen
Hi Bill,
You said: "...It seems to help with maintenance and updating of large,
complex commercial programs..."
Back in the mid-'80s, I used to support a 3-letter software vendor's
Payroll package.
The source was unreadable because of the amount and size of copybooks.
When compiled, the
on
your keyboard? LOL
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Schmitt, Michael
Sent: Tuesday, March 28, 2023 9:41 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] Re: Stop the ragging on COBOL please [was: RE: ASM call by
value]
Yeah, but you can come back
the ragging on COBOL please [was: RE: ASM call by
value]
Yeah, but you can come back to a program years later and understand what it is
doing.
Unlike this:
.if &*i = 0 .th .se *i = 1
.el .se *i = 2
.se *tp = ''
.se *pos = &*tp
...@tbloop
.se *l = '&*&*i
.se *l = &*l + 2 + &$IN
.s
etup on
.if '@SEsetup = 1 .th .me
.se @SEsetup = yes
.im &*
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
billogden
Sent: Tuesday, March 28, 2023 9:26 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Stop the ragging on COBOL please [was: RE: ASM call by value]
>I m
>I myself dislike COBOL for the very simple and personal reason that it's so
>WORDY.
***
I am not a COBOL programmer, except for some very minor attempts a long time
ago. However, I very much respect the proper use of the WORDY aspect. It
seems to help with maintenance and updating of large,
Dr Alan Kay said "...arrogance is measured in nano-Dijkstras", but to my
mind had a dry sense of humour :-)
Roops
On Tue, 28 Mar 2023, 04:22 David Crayford, wrote:
> I think it was flippant Edsger W. Dijkstra quote:
>
> “The use of COBOL cripples the mind; its teaching should,
>
Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Andrew Rowley [and...@blackhillsoftware.com]
Sent: Tuesday, March 28, 2023 7:02 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Stop the ragging on COBOL please [was: RE: ASM call by value]
On 28/03/2023 9:34 pm, Seymour J Metz wrote:
> I once fo
On 28/03/2023 9:34 pm, Seymour J Metz wrote:
I once found myself defending the common idiom
for (;;) {
foo;
}
as a perfectly clear DO FOREVER.
I'm not sure that it is completely clear, it depends on knowledge if
whether the empty statement evaluates as true or false - or just
@LISTSERV.UA.EDU
Subject: Re: Stop the ragging on COBOL please [was: RE: ASM call by value]
yes, I agree with you. It probably needed one informal text where it explained
how to program in it. There is an open source implementation which does a good
job at
https://nam11
<mailto:IBM-MAIN@LISTSERV.UA.EDU>] on behalf of René Jansen
> [rene.vincent.jan...@gmail.com <mailto:rene.vincent.jan...@gmail.com>]
> Sent: Tuesday, March 28, 2023 4:01 AM
> To: IBM-MAIN@LISTSERV.UA.EDU <mailto:IBM-MAIN@LISTSERV.UA.EDU>
> Subject: Re: Stop the raggin
Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Wayne Bickerdike [wayn...@gmail.com]
Sent: Tuesday, March 28, 2023 1:56 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Stop the ragging on COBOL please [was: RE: ASM call by value]
During my early training we were sent to learn Michael Jackson
[was: RE: ASM call by value]
It is very probable that he only liked ALGOL 58 and ALGOL 60, for which he (and
Jaap Zonneveld) made the first compiler (for the Electrologica X1), in an old
school building in a small street, the Boerhaavestraat in Amsterdam, which I
can see from my window across
It is very probable that he only liked ALGOL 58 and ALGOL 60, for which he (and
Jaap Zonneveld) made the first compiler (for the Electrologica X1), in an old
school building in a small street, the Boerhaavestraat in Amsterdam, which I
can see from my window across the river right now. The
During my early training we were sent to learn Michael Jackson structured
programming. MJ quotes Dijkstra a lot, however, I didn't realise that he
was a PL/I hater. That was the first language I learned and still think it
was a masterpiece. I encountered COBOL after I left IBM and it happened to
On Mon, 27 Mar 2023 at 23:22, David Crayford wrote:
>
> I think it was flippant Edsger W. Dijkstra quote:
>
> “The use of COBOL cripples the mind; its teaching should,
> therefore, be regarded as a criminal offense.”
Dijkstra wasn't hot on a lot of languages:
"If Fortran has been called
tances can, in fact, do that. Intelligently devising business solutions
> to business problems in ANY computer language does NOT rot the brain.
>
> It is not funny or acceptable to say so. It never was.
>
> Peter
>
> -Original Message-
> From: IBM Mainframe Discu
er language does NOT rot the brain.
It is not funny or acceptable to say so. It never was.
Peter
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Paul Gilmartin
Sent: Sunday, March 26, 2023 8:14 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ASM call by value
On Sun, 26 M
@LISTSERV.UA.EDU
Subject: Re: ASM call by value
On Sun, 26 Mar 2023 23:18:49 +, Frank Swarbrick wrote:
In COBOL, for example, the following end up doing the same thing.
Do not use CO BOL as an exemplar of programming discipline. Cobol rots the
brain.
--
This message and any attachments
Oh, calling it out is fine. I was talking only about resenting it, which harms
you and does no balancing benefit. You can do the one without the other. Me,
I'm more likely to ignore it, or at least to ignore it longer, but that's a
personal choice.
---
Bob Bridges, robhbrid...@gmail.com,
done, and won't harp on it again.
Peter
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Bob
Bridges
Sent: Monday, March 27, 2023 3:02 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Stop the ragging on COBOL please [was: RE: ASM call by value]
What I'm really thinking
I definitely get having enough of it, old/cranky/ornery or not. And you'll
notice (or maybe you didn't) that I said nothing about ragging on COBOL
programmers. There I'm much more inclined to agree with you.
While I'm making disclaimers, I don't need much in the way of respect when
you're
___
From: IBM Mainframe Discussion List on behalf of
Joel C. Ewing
Sent: Monday, March 27, 2023 9:19 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ASM call by value
All you really need to do a "call by value" in ASM is a special Call
macro (say maybe VCALL) that alloc
Mainframe Discussion List on behalf of
Bernd Oppolzer
Sent: Monday, March 27, 2023 12:49 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ASM call by value
Sorry that I post to the original question;
that's because most of the answers so far missed the point.
Call by value means that a value
11:55 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Stop the ragging on COBOL please [was: RE: ASM call by value]
I am getting increasingly tired of snide or outright dismissive references to
COBOL and by extension to COBOL programmers.
Programmers like me.
Yes, I am also well versed in HLASM, Re
Oops, "typo". I meant "*k = i + j".
From: IBM Mainframe Discussion List on behalf of
Steve Smith
Sent: Sunday, March 26, 2023 7:34 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ASM call by value
My C is rusty... I need to review point
y.
Peter
P.S. -- I love your Erasmus tagline and agree wholeheartedly.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Bob
Bridges
Sent: Monday, March 27, 2023 9:44 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Stop the ragging on COBOL please [was: RE: ASM call by va
I've been resisting the temptation, because it's a repeat, but it's still a
good one:
/* Joke begins */
Jack was a COBOL programmer in the late 1990s who (after years of being treated
as a technological dinosaur by all the UNIX programmers, Client/Server
programmers, website developers etc)
All you really need to do a "call by value" in ASM is a special Call
macro (say maybe VCALL) that allocates "hidden" space for a copy of the
variable value, copies the original variable, and somehow passes that to
the called program, and a programming rule that
Yeah, #3 is the one I keep coming back to. "COBOL? I took a COBOL class in
1975; how can it compete with a modern language like ?"
The same thing with mainframes; they're from the 1950s, and should long
since have gone to a well-deserved grave. They were great in their day,
but... We had this
frame Discussion List on behalf of
> Bernd Oppolzer
> Sent: Monday, March 27, 2023 9:55 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: ASM call by value
>
> What is important to me at least: a parameter passing mechanism where
> addresses are passed
> and the value on the ca
the ragging on COBOL please [was: RE: ASM call by value]
Has anybody used a version older than SNOBOL 4?
From: IBM Mainframe Discussion List on behalf of
Cameron Conacher <03cfc59146bb-dmarc-requ...@listserv.ua.edu>
Sent: Monday, March 27, 2023 8
, not how
you enforce that behavior.
From: IBM Mainframe Discussion List on
behalf of Bernd Oppolzer
Sent: Monday, March 27, 2023 9:55 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ASM call by value
What is important to me at least: a parameter passing
of Bernd
Oppolzer
Sent: Monday, March 27, 2023 9:55 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ASM call by value
What is important to me at least: a parameter passing mechanism where
addresses are passed
and the value on the caller's side cannot be altered (because it has
been copied before, like
say so. It never was.
Peter
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Paul Gilmartin
Sent: Sunday, March 26, 2023 8:14 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ASM call by value
On Sun, 26 Mar 2023 23:18:49 +, Frank Swarbrick wrote:
>In COBOL, fo
Discussion List on behalf of
Bernd Oppolzer
Sent: Monday, March 27, 2023 9:55 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ASM call by value
What is important to me at least: a parameter passing mechanism where
addresses are passed
and the value on the caller's side cannot be altered (because it has
.
From: IBM Mainframe Discussion List on behalf of Bob
Bridges
Sent: Monday, March 27, 2023 9:44 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Stop the ragging on COBOL please [was: RE: ASM call by value]
Peter! I don't think I've heard from you recently; maybe I just wasn't paying
attention until I
nt: Monday, March 27, 2023 7:10 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ASM call by value
Implementation enforces semantics in this case ...
The C implementation (on z/OS at least, but IMO on other platforms as
well) builts a reg1 parameter list
and puts the "value parms" there. With
Peter! I don't think I've heard from you recently; maybe I just wasn't paying
attention until I read this one.
I myself dislike COBOL for the very simple and personal reason that it's so
WORDY. But even when I had to use it a lot (I was a COBOL developer for about
15 years), I was aware that
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ASM call by value
On Sun, 26 Mar 2023 23:18:49 +, Frank Swarbrick wrote:
In COBOL, for example, the following end up doing the same
thing.
Do not use CO BOL as an exemplar of programming discipline.
Cobol rots the brain.
--
This message
+2
-- Original Message --
From: Tom Brennan
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Stop the ragging on COBOL please [was: RE: ASM call by value]
Date: Sun, 26 Mar 2023 23:22:03 -0700
+1
On 3/26/2023 10:55 PM, Farley, Peter wrote:
> I am getting increasingly tired of sn
.
From: IBM Mainframe Discussion List on behalf of
Bernd Oppolzer
Sent: Monday, March 27, 2023 7:10 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ASM call by value
Implementation enforces semantics in this case ...
The C implementation (on z/OS at least, but IMO on other platforms
: Stop the ragging on COBOL please [was: RE: ASM call by value]
Good morning Peter,
SNOBOL??
Geeze that takes me way back.
I had a smile and had to call some old colleagues.
Thank you!
…….Cameron
OOO – March 28, 29, 30 and 31.
-Original Message-
From: IBM Mainframe Discussion List On
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [External] Stop the ragging on COBOL please [was: RE: ASM call by
value]
I am getting increasingly tired of snide or outright dismissive references to
COBOL and by extension to COBOL programmers.
Programmers like me.
Yes, I am also well versed in HLASM, Rexx
IBM Mainframe Discussion List on
behalf of Bernd Oppolzer
Sent: Monday, March 27, 2023 2:49 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ASM call by value
Sorry that I post to the original question;
that's because most of the answers so far missed the point.
Call by value means that a value
have to deal with call by name.
From: IBM Mainframe Discussion List on behalf of Bernd
Oppolzer
Sent: Monday, March 27, 2023 2:49 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ASM call by value
Sorry that I post to the original question;
that's because mos
.
From: IBM Mainframe Discussion List on behalf of
Bernd Oppolzer
Sent: Monday, March 27, 2023 2:49 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ASM call by value
Sorry that I post to the original question;
that's because most of the answers so far missed
On Sun, 26 Mar 2023 21:35:13 + Frank Swarbrick
wrote:
:>Can the MVS CALL macro be used to call a C function with "value" parameters
(rather than reference parameters)?
What does "call by value" look like?
Does the subroutine definition indicate that the parameters are by value? If
not,
I would like to add:
if you pass the address of a constant field to the called prog using the
CALL macro,
this looks like call by value, but in fact you have call by reference
again, because you
pass an address in the reg1 list.
This is what PL/1 for example does, if it builds and passes a
Sorry ... in some places: replace "caller" by "called prog" ...
Am 27.03.2023 um 08:49 schrieb Bernd Oppolzer:
Sorry that I post to the original question;
that's because most of the answers so far missed the point.
Call by value means that a value is passed to the caller;
call by reference
Sorry that I post to the original question;
that's because most of the answers so far missed the point.
Call by value means that a value is passed to the caller;
call by reference means that a reference (technically: an address) is
passed to the caller.
In ASSEMBLER:
CALL
problems in ANY computer language does NOT rot the brain.
It is not funny or acceptable to say so. It never was.
Peter
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Paul Gilmartin
Sent: Sunday, March 26, 2023 8:14 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ASM call
the brain.
It is not funny or acceptable to say so. It never was.
Peter
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Paul Gilmartin
Sent: Sunday, March 26, 2023 8:14 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ASM call by value
On Sun, 26 Mar 2023 23:18:49 +, Frank
myfunc([0]);
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Tony Thigpen
Sent: Sunday, March 26, 2023 3:34 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ASM call by value
Structures are passed by address, not value.
To
On Sun, 26 Mar 2023 21:34:23 -0400, Steve Smith wrote:
>My C is rusty... I need to review pointer/address-of syntax. The idea for
>the 3rd argument was to show one "passed by reference"; in any case
>modifiable by the subroutine.
>
>But where did x and y come from?
>
Maybe he meant i and j.
On
, "*k = x + y".
>
> From: IBM Mainframe Discussion List on behalf
> of Frank Swarbrick
> Sent: Sunday, March 26, 2023 5:52 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: ASM call by value
>
> I'm guessing he meant "int *k" rath
n <042bfe9c879d-dmarc-requ...@listserv.ua.edu>
Sent: Sunday, March 26, 2023 6:14 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ASM call by value
On Sun, 26 Mar 2023 23:18:49 +, Frank Swarbrick wrote:
>True, but "passing by reference" and "passing a 'reference' (pointer/a
On Sun, 26 Mar 2023 23:18:49 +, Frank Swarbrick wrote:
>True, but "passing by reference" and "passing a 'reference' (pointer/address)
>by value" are the same.
>
No. When "passing a 'reference' (pointer/address) by value" the called
subroutine
receives a *modifiable* pointer/address value.
Also, "*k = x + y".
From: IBM Mainframe Discussion List on behalf of
Frank Swarbrick
Sent: Sunday, March 26, 2023 5:52 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ASM call by value
I'm guessing he meant "int *k&q
I'm guessing he meant "int *k" rather than " k".
From: IBM Mainframe Discussion List on behalf of
Paul Gilmartin <042bfe9c879d-dmarc-requ...@listserv.ua.edu>
Sent: Sunday, March 26, 2023 5:49 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subj
I think this is exactly what I am looking for. Thank you.
From: IBM Mainframe Discussion List on behalf of
Steve Smith
Sent: Sunday, March 26, 2023 5:35 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ASM call by value
I forgot to mention, to pass by value
On Sun, 26 Mar 2023 19:35:59 -0400, Steve Smith wrote:
>I forgot to mention, to pass by value with CALL, you need [a] register[s].
>e.g.:
>void foo(int i, int j , k)
> {
> k = i + j;
> }
>
That shouldn't be legal. In fact, gcc gives me:
cc tinyc.c -o tinyc
tinyc.c:3:25: error:
I forgot to mention, to pass by value with CALL, you need [a] register[s].
e.g.:
void foo(int i, int j , k)
{
k = i + j;
}
* ASM
L R2,xyz
LHI R3,1
CALL FOO,((R2),(R3),BAR)
...
XYZ DS F
BAR DS F
Depending on # of registers available vs. # of value parms, CALL may become
infeasible.
sas
101 - 200 of 207 matches
Mail list logo
