× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I always took a differing approach and NOTHING goes in QGPL.

If your commands use PRDLIB then it shouldn't be an issue placing data areas and libraries in your own libs. Then they can be qualified or called using the library list.

I seem to recall in the early days QGPL got mucked up between releases.

Anyhow I'm sure people are all over the board in their use of QGPL.

Regards,
Richard Schoen
Web: http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx
Phn: (612) 315-1745
----------------------------------------------------------------------

message: 1
date: Thu, 8 Aug 2019 19:34:28 -0500
from: B Stone <bvstone@xxxxxxxxx>
subject: Re: Use of QGPL library for custom objects

My software stores it's license keys in QGPL. Never had a problem in over
20 years and thousands of installs from V2 to V7.

Why? I know the library will always be there. It's like using /tmp in the IFS, sort of, to me. the only issues I've ever had are authorities, but I have a FAQ that says to check that first if there's an issue.

Now, why not keep it in my own library? I hate to say it, but library lists seem to be becoming more of a challenge as the torches are passed from the gatekeepers of yore to 3rd parties, or new people.

If there were two things I wish everyone should know it would be how a library list works, and how to capture data from a screen copying and pasting the text vs sending a screen shot.

Bradley V. Stone
www.bvstools.com


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.