go to post Joel Solon · 22 hr ago Anything can be achieved without instance methods. The point here is that instance methods exist in object-oriented systems because they are considered a good, straightforward way to achieve certain things. In the case of unit tests sharing information using properties, that approach saves you from having to pass info around as method arguments, or declaring a list of public variables.
go to post Joel Solon · May 24 I've also used Studio for 20+ years. I can still remember how much better it was than what we had before. We can all still use Studio if we want; it's not a forced divorce. But we hope that VS Code -- ObjectScript's features will make you comfortable enough to decide to do a conscious uncoupling. And as Frank Sinatra sang: "Love's much lovelier, the second time around." And he could have sung that at the Diplomat Hotel in Fort Lauderdale in 1974, where coincidentally InterSystems is hosting our Global Summit this year!
go to post Joel Solon · May 24 In the interest of accuracy, Studio does allow looking at OREFS to see their properties (View As > Object, or Dump object).
go to post Joel Solon · May 23 Why are unit test methods instance methods? Since a running unit test is an instantiated object (%RegisteredObject), the unit test class itself can have custom properties, and the instance methods can use those properties as a way to share information. For example, initialize the properties in %OnBeforeAllTests(), and then access/change the properties in the test methods.
go to post Joel Solon · Apr 10 LAST_IDENTITY() returns the ID of the last record inserted, updated, or deleted. This is very useful from ODBC/JDBC. From within an ObjectScript method, you can access this directly instead of running an additional SELECT statement: For Embedded SQL, you can use the %ROWID variable. For Dynamic SQL, you can use the resultset.%ROWID property.
go to post Joel Solon · Feb 14 @Nicholai Mitchko's example above is Python calling an ObjectScript method that has pass-by-ref arguments, and that works as he described. I wondered if Python methods could be written to return values in their arguments, despite the fact that Python doesn't have pass-by-ref arguments. The answer is "yes," but only if the caller passes in a data structure (like a list or a dict) that the Python method modifies. Otherwise, arguments to a Python method called from either ObjectScript or Python can't return values.
go to post Joel Solon · Dec 21, 2022 If you make a loooonnnnng $piece-delimited string, and a lonnnnnnnnng $list, and you loop 1000000 times, accessing random pieces and random $list items, and sum up the time, and divide by 1000000, you'll find that for access, $lists are faster than delimited strings. At least that's what I saw when $list first appeared. But my mentor from that time said "Yes Joel, they are faster, but $list was added to ObjectScript so that we wouldn't have to worry anymore about delimiters, and sub-delimiters, and sub-sub-delimiters, etc."
go to post Joel Solon · Dec 16, 2022 True. I personally am not a fan of using #dim in any way other than: #dim variable as objectclassname because it makes it clear that #dim provides code completion for object variables, which is the functionality I care about. Yes, I know it also provides variable documentation for developers who are used to declaring datatypes in other languages The other documented options: #dim variable as objectclassname = initialvalue (ok, but I prefer #dim followed by set) #dim variable = initialvalue (there's no reason to use #dim to do what set does) #dim variable as non-objectclassname (this is documentation only; no code completion is provided) #dim variable as list/array of objectclassname (again, documentation only; no code completion)
go to post Joel Solon · Dec 8, 2022 It's not a big difference between Studio and VS Code - ObjectScript here. Studio automatically does the #dim for you when you do a %New() or %OpenId(), and VS Code - ObjectScript doesn't. But #dim is still necessary in both IDEs for referenced or returned objects: set person = ##class(Simple.Person).%New() // Studio WILL provide code completion for person, VS Code WON'T #dim address as Simple.Address // without #dim, neither Studio nor VS Code will provide code completion for address set address = person.Address #dim rs as %SQL.StatementResult set rs = statement.%Execute(args) // you'll get code completion for rs thanks to #dim
