Re: [Jprogramming] testing for J version or later

2023-12-24 Thread chris burke
Since stdlib is not updated for older versions of J, addons that depend on the J version will have to use their own test like your original jversion function. Alternatively, set the addon manifest RELEASE for 9.4 or later and just support the new version number. The 9!:14 result is then parsed in

Re: [Jprogramming] testing for J version or later

2023-12-24 Thread Ian Clark
I've a better idea. Establish a new system flag called (say) VERSION_z_ and assign it within stdlib.ijs (c/f IFJHS or JLIB) the integer form of the J version (currently this would be VERSION_z_ = 951). Then ~addons/math/cal/cal.ijs, or some other utility with a version dependency, could test for

Re: [Jprogramming] testing for J version or later

2023-12-21 Thread Raul Miller
Hmm... only if we're updating stdlib, supporting versions of J back to 4.0.1. A worthwhile effort, though, if someone was actually tackling those issues. Otherwise, I think an idiom would be about as good as it gets. -- Raul On Thu, Dec 21, 2023 at 9:24 PM Ian Clark wrote: > > For those of us

[Jprogramming] testing for J version or later

2023-12-21 Thread Ian Clark
For those of us digital archaeologists running back-levels of J, it would be nice to have a robust test for a given version of J or later which tolerates versions down to 4.01, say. What represents best-practice? The best I can come up with is: jversion=: 3 : 0 ". 'j.' -.~ '/' taketo 9!:14''