Are you running preemptive processes in 4D v16?

Poll choices
Posted 2 years.

1 Comment

  • Jody Bevan - 2 years ago

    With version 15 we took the opportunity to rewrite our shell from scratch. As is usually the case this is about an 8 month project. Therefore we moved up with each new release of 4D so that our shell is written for 16.2. Therefore we converted our code to take advantage of preemptive processing where we could, as well as many other areas. Since this is our shell the first thing we do is write code that is generic so we can quickly create new uses for preemptive processing. We also write example code, and documentation for our shell users so they know how to add them in. Exciting development. Really looking forward to taxing our 16 core computers with this code to see the performance.

    We had already built in object arrays and dot.notation for our C_Objects so we did not need to jump to a later release of v16. As well, we were already writing our code to make use of our dot.notation for our forms so we have not jumped to a later release of 4D.

    It is great to see that 4D and us are of like mind of the future direction of 4D thus far. We are really looking forward to a mature 4D Write Pro that can replace all we used 4D Write for. We like a lot of what they have already done with 4D Write Pro.

    ARGUS Production Inc. team