Thanks - that is what I expected.  I think that the older git source control hooks will likely end up being frustrating for you working in that mode.  Check out Deltanji, or we will see if there is any chance of git-source-control working for you.

thank you for clarifying.  we'll see what Pravin and Tim say about git-source-control on Caché

@Token Ibragimov - is your intention to have only a single developer working on this Linux system, or will many developers be making changes?  The reason that I ask is that while there have historically been a number of Caché git source control hooks which have been created and discussed on this community (a search here will find several examples), they have all assumed the normal git way of working which is a single developer per environment.  This has caused challenges with the typical way of developing on InterSystems products, which is many developers against a single instance.  This is why my team created git-source-control, in order to make git available in a way that works more seamlessly with our products.  

If you are going to be stuck on Caché for a while, you may want to consider other source control options which are designed to work natively with the platform, like Deltanji (https://georgejames.com/deltanji/).

Let's see what Pravin and/or Tim think about git-source-control working against Caché 2017.1.

@Timothy Leavitt / @Pravin Barton - can you please weigh in on whether it is possible to run git-source-control on Caché 2017.1?  I know the atelier APIs are present in that version (in at least an early iteration) but are there other things missing which would prevent it from working?

@Token Ibragimov - curious, do you have a rough timeline as to when you'll be moving to InterSystems IRIS?

Thank you very much for taking the time to report the solution and great resources back into the community!

You might want to bookmark this one instead, so you're always looking at the latest documentation:

https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cl…;

creative!

please do!!

not directly - this is grabbing the Length ($Length()) of the variable X, using "," as a delimiter of the string.  So the counter 'i' will run from 1 to the length of X, and then each iteration will grab the next piece of the string (, delimited again)

You beat me to it @Chris Stewart!

I am not sure that all of the docs are public until the product is fully released.

Glad you figured it out!  Thank you for letting us know that it was resolved and was a configuration issue.

@David.Satorres6134  - that is a TREMENDOUS example of leveraging embedded python to avoid reinventing the wheel in ObjectScript!  This very nicely demonstrates the value to people like me, who prefer to work in ObjectScript whenever possible, of having embedded python as a bridge to thousands and thousand of reusable libraries.  Thank you for weighing in :)