Found part of the thread.
NG : Tony T, Jan 25:
Autodesk has already made it clear that they're not going continue supporting the (entxxxx) style functions for accessing and modifying entity data. In fact, newer releases of some vertical products do not even support it, and the only way to access the custom objects in those applications is via their ActiveX interfaces.
While you can continue to do relatively simple programming with that style of coding, it is obsolete and certainly does not have any future. Considering how cryptic DXF codes are, I can't see why anyone would want to program that way any longer, given the ActiveX API, but in LISP, the syntax is a bit convoluted, and you have to write a lot more code (the advantage is that it is more explicit and therefore makes the intent of the code much clearer, at the expense of brevity).
ActiveX is fine if you use VBA or another imperative language with a rational OOP syntax, but for LISP it is simply not my preferred way to code.
The point to the comment about the entxxxx style of LISP coding, is that someone was using it to "copy" entities, but didn't realize that it was not really doing that, and hence, could have undesireable effects in some circumstances.
That thread is what I'm referring to.
You can do what you like.
Bob
