|
> From: Tom Liotta > > Are you saying you "HAVE" to suffer another expense to use /free? > What expense? Actually, as it turns out, Jon says there's an automatic conversion option in CODE/400 (and hopefully that will get moved to the LPEX editor in WDSC). The additional cost was from the statement that I should just use Linoma's tool. > All this time I've been thinking that all I had to do was wrap in > /free<>/endfree and I could use new features. That actually seems > much easier than converting cycle-based file processing to > full-procedural or than removing user-defined display formats to > make way for DDS WINDOW() support or... True, you CAN use the /free container. It gets really ugly, but you can use it. So, in the long run, all my arguments are really about whether it's okay to make people use /free and /end-free to mix new BIFs with old MOVE instructions. I've made my point, and I'm unlikely to do anybody any good continuing on, so I'll just leave it here. Joe
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.