in a purely garbage collected system, a circular reference is not a problem: if neither of the objects involved is referenced by any other object, then both are garbage collected.
the additional parameter doclocs is used to record the uris of the loaded schemas along a particular path of imports or includes to avoid an endless recursive call when a circular reference occurs.
this kind of circular reference frequently occurs when closures are used with client-side programming in ie.
这种闭环应用通常发生在在ie客户端编程中使用闭包的时候。
one has to be careful about doing this however, as it can create a circular reference that will interfere with both the lisp and .net garbage collectors.
the seeming circular reference — where t extends something parameterized by t — is not really circular at all.
表面上看似循环引用 —t扩展经过t参数化的内容 —实际上并不是真正的循环。
if you use the soap encoding as the message bindings, the circular reference can be easily represented by applying soap encoding rules on the cyclic graph by using the multireference accessors.