Release 2.7.22344 is now available on the website

George
Administrator

Posts: 4,052

Release 2.7.22344 is now available on the website Dec 10, 2022 13:08:40 GMT -5

Quote

Post by George on Dec 10, 2022 13:08:40 GMT -5

Hi,

At long last, a new release.

This one contains EFT (Extended File Types) which is a replacement for the old PROFiLE USING support. If you are a current user of PROFILE USING, no worries, all your current USING setups will be automatically converted to the new EFT support, you have NOTHING to do. And if you revert back to an older SPFLite release, your old USINGS are still intact. After you are comfortable with this new support, you may then, at your leisure, remove the old PROFILE entries that specified USING.

This release also contains a very large number of bug fixes and other miscellaneous enhancements. It is well worth the time to browse the Change Log.

George

George
Administrator

Posts: 4,052

Release 2.7.22344 is now available on the website Dec 10, 2022 15:05:10 GMT -5

Quote

Post by George on Dec 10, 2022 15:05:10 GMT -5

Robert: Probably not, more like 'of course not', there's no way I will ever be able to keep track of all that stuff. Quite simply, we have to stop changing stuff, there's too many interactions between various SPFLite facilities to manage. I think it's time to truly shut down enhancements and just try and correct what we've got.

George

[UPDATE]

Looked at XFORM Write. I'm just going to drop the RC4 option. The macro will either Write the file (RC 0), or fail the write (RC 8). The option to 'choose not to write' just goes away. I don't see this as a problem.

G.
[/UPDATE]

Last Edit: Dec 11, 2022 11:05:47 GMT -5 by George

George
Administrator

Posts: 4,052

Release 2.7.22344 is now available on the website Dec 12, 2022 11:31:51 GMT -5

Quote

Post by George on Dec 12, 2022 11:31:51 GMT -5

Robert: RC 4 went away when it turned out that it collides with some other internal uses of RC to determine the logic flow after a command. Wasn't a lot of choice, internally there are a lot of RC values in use, and I simply wasn't going to review every error message in the program and design a new RC structure to replace the existing one. Yes, you can call me lazy.

And as for XFORM itself. I'm hard pressed to even think of a circumstance where RC 4 could be productively used.

a) I really doubt there's ever been enough XForm usage to even justify XFORM itself.

b) And any XFORM macro that supports WRITE at all, is well aware that STATE is blown away.

c) So how many XFORM macros, that support WRITE, are also going to find a reason to NOT WRITE when they're called, and expect STATE to be preserved?

d) Also, if a file needs XFORM to be read, it's probably some weird format and simply wouldn't have had STATE data anyway.