Topic: Dictionary Functions (vlax-ldata)

[ChrisCarlson]

I can't seem to find much documentation aside from this?

http://help.autodesk.com/view/ACD/2015/ENU/?guid=GUID-F5F376FF-9BC2-476A-9EA9-1455D28DE264

There was a previous debate here about xdata vs ldata and the general consensus was to avoid ldata because AutoDesk modified the format once, and they could do it again?

-Is either method a more native LISP approach?
-If the only issue is AutoDesk modifying ldata format, for basic setting and retrieving of data, ldata seems leaps and bounds easier than xdata.   

[dgorsman]

For me its not about whether LDATA will be changed or dropped.  Its that XDATA and XRecords provide better flexibility.  Yes, LDATA is easier *but* that comes with limitations which might bite you later on as you take on more complex work.

[hermanm]

AFAIK, the primary modern objection to ldata is lack of straightforward COM or .NET interface. In case you wish to access existing ldata using either of those, you may find it difficult or even impossible to do. If memory serves (and I am not certain it does) the great Tony T. once showed a roundabout way to access ldata using COM, but I do not recall the details.

If your intent is to access ldata solely via LISP, then I agree it is easier than XRecords, and also more self documenting. I have experienced no issues using ldata.

[jjurkus]

I used ldata for a while, before converting everything to xdata. If I remember correctly, with ldata, you have to convert everything to a string.
I also don't know if ldata shows up using "(entget(car(entsel))'("*"))" on an object.