× 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.



rob@xxxxxxxxx wrote:
Hans,

What additional checking is done with LIKEREC that isn't already done with EXTNAME? Don't they both pull in the field names and attributes? I realize that once "you've let the cat out of the bag" by creating LIKEREC it's hard to take it away. But if they do the same checking, I'd just as soon use EXTNAME.

Can you change LIKEREC so that we may add additional fields to it? Or at least overlays?

Rob Berendt

Rob: As I suggested, one of the design features of LIKEREC is that you can't add subfields to it. Thus, it can be used as the result of record I/O with confidence that the data structure matches the record precisely. Do you want to be able to read into a data structure that does not match the record? What exactly are you trying to accomplish?


Cheers! Hans



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.