|
I am sorry if I seem to attacking a personal grooming habit of yours. It's just that I have a few in my shop that are loath to use this honking /COPY we have because they detest unreferenced variables. Therefore they either cut and paste the code in, or redefine the structures using their own variables. To me, it sounds like they are creating more problems then they are solving. But I don't press too hard. I don't want to get labeled "doesn't play well with others". We are trying to compromise by breaking down the honking /copy into several smaller ones. Now the honking /copy has the others as /includes. Therefore if you like just a few of the structures - no problem, if you just want it all and want to get back to coding - no problem either. So now the honking /copy looks more like /INCLUDE ROUTINES/QAPISRC,QCAPCMD /INCLUDE ROUTINES/QAPISRC,SYSTEM *************************************************************************** * System API's - User spaces * *************************************************************************** /INCLUDE ROUTINES/QAPISRC,QUSDLTUS /INCLUDE ROUTINES/QAPISRC,QUSCRTUS /INCLUDE ROUTINES/QAPISRC,QUSRTVUS /INCLUDE ROUTINES/QAPISRC,QUSPTRUS And so on. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin
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.