ed
independently from its object - see <a href="#cast"><code>CAST</code></a>.
<p>
As long as a container is accessible in Lisp its underlying .NET
object won't be garbage-collected in the CLR.
<p>
Whenever a RDNZL function accepts .NET objects as arguments (except
for the first argument of <a href="#invoke"><code>INVOKE</code></a>, <a href="#property"><code>PROPERTY</code></a>, and <a href="#field"><code>FIELD</code></a>) you can also
provide the corresponding "native" Lisp objects as long as they can be
co