On 9/06/2021 3:10 am, Paul Gilmartin wrote:
On Tue, 8 Jun 2021 22:16:54 +0800, David Crayford wrote:
Is FLOWASM open source or do you have a mates shared version?
Is 2009 good enough for you?: https://www.phoenixsoftware.com/ftp/demo/?C=M;O=D
Perfect. I have to say, that's a superbly documented piece of code.
As I mentioned earlier in this thread we are looking at using FLOWASM
for Metal/C code, both internal and Zowe. The problem with Zowe is that
FLOWASM will probably not be installed at most sites that want to build
Zowe Metal/C code.
??? FLOW should be irrelevant to most C. Is Metal/C a recidivist?
Certainly not. Metal/C is for systems programming which requires __asm()
blocks that invoke HLASM macros. Continuation characters are a PITA in
HLASM, in C they are a nightmare which has led to some
unfortunate workarounds [1]. FLOWASM solves that problem perfectly.
Introducing SPMs also solves the problem of duplicate labels when the
optimizer inlines code. We have to compile with NOLINE right
now which disables one of the most useful optimizations.
I brought up introducing FLOWASM into Metal/C code in a code review last
week and we've opened a ticket for it.
[1]
https://github.com/zowe/zowe-common-c/blob/2d18745553d233143004249802040ae4da5e82b9/c/cmutils.c#L342
I'm wondering if a pre-build step that copies FLOWASM into a
userid.FLOWASM.LOAD library and then sets a STEPLIB environment variable
would be acceptable.
-- gil
----------------------------------------------------------------------
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
