I don't understand what you mean by "until the list values may contain any set of characters".

Nor do I understand the purpose of the second line of your terminal transcript above. None of your subsequent lines do anything with your local variable called list

I found this answer interesting. A bit of browsing in the history at http://docs.intersystems.com/cache.html shows that the ability to disable an index arrived in 2013.1.

Looks like we now have HTML formatted digest emails. Was that new in the May 30 update?

Did someone forget to sign the Windows kits? When I use the 64-bit Ensemble one on my Windows 8.1 machine I was warned that the EXE came from an unknown publisher.

Examining the Properties dialog for the EXE I see this:

By comparison the one for build 645 has a "Digital Signatures" tab with an ISC entry:

Amit, you have tagged this as "Developer Community". Perhaps you originally posted it to the group, which as I understand things is primarily intended for feedback about this online forum, https://community.intersystems.com

I think that posts to that group are intentionally not shown on the homepage feed of new postings.

It looks like it's now in the HealthShare group, but maybe changing its tag will help other people find it and respond.

Murray, the documentation section you link to recommends excluding certain directories as well as specific files. This makes me nervous, as having a scanning exclusion on an entire directory surely offers a safe haven for malware to write a payload that it subsequently executes. Can you explain the reasons for excluding entire directories?

"Ask and it shall be given unto you" - nice to see that page has now been updated.

Maybe worth adding a mention of 2016.3 FT to this page.

Here's one change I'm particularly pleased to see:

Ability to Create Namespaces that are not Enabled for Ensemble
In certain circumstances, it is useful to create namespaces that are not enabled for Ensemble. In this release you can do this by clearing the Make this an Ensemble namespace checkbox when creating a new namespace. 

Maybe revise the message to read "Package name can contain dots but cannot start or end with a dot", or something similar.

Thanks for your explanation Mark.

Interesting to know that the ZZW command was removed, leaving only the full-form ZZWRITE one. Our Command Line Extensions implemented ZZW and ZZWRITE as synonymous. Your ZZWRITE implementation takes precedence over our ZZWRITE but at least our implementation remains accessible via ZZW.

Ideally you guys would establish a policy one way or another, document it, then stick to it going forward, applying the rule consistently to commands, functions and system variables. In the past you've typically added Z* things but not ZZ* things, for example $ZCLASSMETHOD().

Thanks for posting this. I shall try and remember to use the link routinely for my exploration of the docs, as a way of testing the beta.

Yes, a useful command but I think it's inconsiderate of InterSystems to be annexing the ZZ* command-space. The facility for sites to extend the language with their own commands by writing a %ZLANGC00 routine (see here) has been useful and we at George James Software have for many years offered a free download called Caché Command Line Extensions. We deliberately made all our commands begin with ZZ in an effort not to clash with future InterSystems extensions, but our ZZW extension was subsequently overridden by the ZZW command InterSystems added in 2013.1. It seems it's only a matter of time before you sequester other commands from us.

For those of us outside InterSystems, 1.0.145 and 2016.2.0.645 are the latest versions currently available.

EDIT: I typed too soon. It turns out 1.0.158 was published on the update site overnight. Maybe Mike's problem will be resolved by him updating to that.

Nice article. One comment: I get nervous when I see code that swaps namespace without taking steps to swap back again afterwards.