This is interesting stuff and it's good to revisit this as ObjectScript evolves. In the old days, there was advice about things like this:

  • set a=1, b=1, c=1 was faster than set (a, b, c) =1
  • if a]"" was faster than if a'=""
  • etc.

But we always reminded people that these things could change from platform to platform, and that extra database references were usually much costlier than the differences between coding things one way vs another.

So, Tim, if you've got the time, please tell the Community if your tests show different values on Windows vs Linux vs Unix vs OS X. And (this might be harder), give us your opinion on a "tipping point" or a "when to care about this point"; that is, if the delimited or list string has fewer than N pieces/items, it really doesn't matter which method is used, but above N, use the $listlength method, and above M, use $listnext. Something like that.

I never updated this post with the workaround, sorry! The problem is with Secure Storage. You can reset it by going into Atelier > Preferences > General > Security > Secure Storage. Click the Contents tab. Under com.intersys.eclipse.connmgr, you'll see an entry for the connection to the Caché server. Delete that entry, and you should be able to recreate the server connection.

Also note that Caché developers will be able to choose to use Atelier even if the Caché server is not yet on v2016.2 or a later version. Steps:

  • Use a local installation of v2016.2 integrated with their chosen source control system to edit classes and routines.
  • Use Atelier’s export feature to export the file(s) to our standard XML format, and import those files on the Caché server.

Each developer can choose between familiarity with Studio and easy integration with the server (with perhaps no integration with source control), or familiarity with Eclipse and easy integration with source control (with an extra step or two to integrate with the Caché server).