|
Joe, This is the way we do it, put this definition in the /copy member with the prototypes. I have had a couple of instances where I put the type definitions into their own copy member that is /copy'd into the prototypes. This is because I ran into an instance where something needed the type definitions and wasn't calling any of the procedures. If you have several of these definitions you can base them all on the same pointer. We even have some definitions that aren't from a database file so just define a field and use based also. We use _t on the end of the field names to denote type definition fields but that is just our convention. Scott Mildenberger --- Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx> wrote: > > My current thinking is to use a based external DS with a > prefix. This > would "waste" only the space for a pointer, thus: > > d __SCCKW e ds extname(SCCKW) based(__) > prefix(__) > d SccIOKWClear pr > d ID like(__KWDFID) value > d Format like(__KWFMT ) value > > (The double underscore is just an idea; I could just as easily > use a > double @ or something else to try and minimize collisions.) > __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com
As an Amazon Associate we earn from qualifying purchases.
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.