COM API Version 2: Thanks for Ongoing Improvements

I just noticed that the COM API Specs had been updated to Version 2, and some new goodies added.

Firstly, many thanks for the new DetailsKind properties for some of the objects. These will make scripting a little easier and will make for clearer code if different possible kinds might be returned. Many thanks for this!

(Note: the API docs say this string may be a null. Actually its the blank, or length-zero string. Not a null reference. A blank string is much nicer than a null ref for simple coding.)

The LogosDataType.ScanForReferences(someText) is not yet exported from 4v1 Beta 7, so I look forward with hope as to what goodies this might permit. Bring it on please ...

My view is that the API still needs some more features before its useful for much that can't be done as easy using URIs, but I welcome that work is still ongoing with the API.

Thanks Team Logos.

Find more posts tagged with

Comments

Bradley Grainger (Logos)

(Note: the API docs say this string may be a null. Actually its the blank, or length-zero string. Not a null reference. A blank string is much nicer than a null ref for simple coding.)

This was actually a matter of debate in the office (see discussion of NULL at http://blogs.msdn.com/b/ericlippert/archive/2003/09/12/52976.aspx), but we tested with both C# and VB.NET and both left the 'null' as 'null' (and didn't convert it to an empty string). Which language are you using to write your COM client?

JimTowler

https://community.logos.com/discussion/comment/161713#Comment_161713

I am using Microsoft Visual Basic 2010 Express mostly.

I did some more testing after your reply above:

1) The VB IsNothing(whatever.DetailsKind) returns TRUE if there is nothing there, so it IS A NULL after all.

2) A test such as: IF (whatever.DetailsKind = "") THEN, also returns TRUE, so it seems VB is happy to treat a NULL string as a zero-length one too. I need to watch for this "trap" when it might make a difference.

Based on result (2), my first post was sort-of right, yet wrong all at the same time. Thanks to automatic casting and conversons ... [:)]

(In C or C#, a line such as [ if thing = "" ] will always be true, as its an assignment of course, unlike VB. Corrrect C is [ if thing == "" ])