Thanks
First off, I am assembler programmer by trade I did learn C/C++ doing some
TCP/IP stuff from an Assembler Server Started task.
It would display the data program listing from a sysadata on Windows.
I would like to use that code on z/os.
If you say clang, is the way to go okay.
You also say use the clang compiler instead of MSVC I hope I don’t end up with
a millon more compile errors using clang as everything compiles cleanly using
MSVC.
I debug under Unix.
Since I am going to run this from z/os its going to be LE with runtime option
POSIX(ON) ? right ?
Now as far as the doc for OPEN XL C++
I got a compile error using map::insert invalid call.
CCN5218 (S) The call does not match any parameter list for "insert".
Is referenced the following statement.
auto ret = procpointer->extsymcollector->insert({ *s, *exsympointer });
the compiler initially gave me a problem with '{'
I took it out.
auto ret = procpointer->extsymcollector->insert( *s, *exsympointer );
then I got the above error
My question is if I got to Open XL C++
Regarding documentation for let's say map::inset I would reference Clang/LLVM
link you sent me earlier.
I hope I don’t open a pandoras box if I change to clang and re-compile all my
windows code.
Thanks for your help.
-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of
David Crayford
Sent: Thursday, February 2, 2023 2:46 AM
To: [email protected]
Subject: Re: Open XL C++ debugging
On 2/2/23 02:42, Joseph Reichman wrote:
> Was looking at the compiler reference kind of small handful of options
> compared to pages and pages for XL C\C++ compiler option
Haha! You're joking right? There's significantly more compiler options as it's
a port of clang
https://www.ibm.com/docs/en/SSUMVNF_1.1.0/pdf/Clang.pdf#page=219.
> One very important question when I looked at the Manuel doesn’t
> specify how to debug it
How do you debug any C/C++ program in z/OS UNIX. You compile with the "-g" flag
which creates DWARF debugging records and the use dbx to debug. The interesting
thing about Open XL C++ is that it embeds debug information into the binary as
opposed to creating a *.dbg side file.
My advice to you use the XL C/C++ v2.4.1 web deliverable xlclang. I don't think
you need to be on the bleeding edge of language standards :)
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
