Re: Binder Language

Binder language is one of those things that is just too darn simple to
grasp easily. I think it took 3 sessions at COMMON for it to finally sink
in that I was over complicating it.
Jon Paris' signature in my RPG Redbook is "I thought you knew this stuff
already!". Just double checked his autograph.

On Wed, Jul 10, 2024 at 2:25 PM James H. H. Lampert via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

I've managed to find my altered binder source for our custom version of
HTTPAPI, and it was indeed done to create an HTTPS-enabled version that
would be drop-in compatible with a non-HTTPS version 1.21 (at the
expense of it being drop-in compatible with any other HTTPS-enabled
version).

And it looks like it would be easier than I thought to update this to a
more recent HTTPAPI.

I'm currently reading up on service program creation and binder
language. And I'm not sure I understand how multiple STRPGMEXP blocks
work, or how the PGMLVL parameter works with regard to them. Can
somebody point me to something that will explain it in terms even my
aging "little grey cells" can process?

--
JHHL
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.