Re: Load CL variables from SQL example

On 8/20/2019 1:39 PM, John Yeung wrote:

When someone tells you your Python code isn't Pythonic, they are
telling you that what you are trying to accomplish in Python can be
done in a more elegant way, or a way which is closer to what the
language design encourages, or a way which has come to be the
preferred way by Python experts who have the benefit of experience.

I do hear that message, but first I hear 'that looks funny'. I don't
view that as a harsh criticism. 'Funny' might be the mildest word
starting with 'fu' that's been addressed to my code :-)

Are you then saying that if I am trying to accomplish something on the
IBM i (such as building a Web application), that the more elegant way,
the way that IBM i is designed to support, and the way that experts
have coalesced around, is to do everything (or as much as possible)
with CALL/PARM? Because otherwise it "looks funny"? Imagine the giant
pile of funny-looking that is a JavaScript application built on
Node.js, running on the i!

I'm not sure I quite managed to say that everything ought to be done
with CALL/PARM, but it's clear I could have done better.

Your comparison is tantamount to saying "anything that isn't
database-oriented business logic on the back end and 5250 green screen
on the front end looks funny". Or, if not *quite* that drastic, then
"anything that isn't written in CL, RPG, COBOL, and maybe some C,
looks funny".

I tried reading my response again, and I see what you mean. I should
have realised that not every individual post carries the context, the
history, that I have inside my own head, and I should have clarified the
context. I thank you for your gentle reminder.

The overarching context of my remarks on interoperability is this: I
have a large, functional, vital body of existing RPG and CL code that I
would like to extend by grafting on functions from the open source
world, PASE, and yes, my old friend Rexx.

Rexx (like Python) extends my RPG/CL, not ever the other way round.

'Looks funny' isn't to put down unstructured streams (in lieu of
CALL/PARM), but to note that it's not a natural (Pythonic?) way to view
program interoperability on this platform. Which is why I presented
actual working examples of how to do it. I'm afraid my word choices
weren't the best. I was hoping for:
a) CALL/PARM doesn't work with Rexx
b) Unstructured streams don't look like CALL/PARM
c) Here is an example of unstructured streams that anyone can try

Always a pleasure exploring programming with you John!