Re: v11.4 : 67 is a list reference

Jérôme

Thanks for that clarification. I don't remember ever coming across the
problem myself, and had hoped that the memory separation would be
enforced by 4D - but bugs will be bugs and I wondered if somehow this
one had got through the net.

2009/7/3 Jérôme Pupier <jpupier@...>:
> David,
>
> That was true in the very first v11. It was possible to clear intenal
> 4D lists, that leads to stange behaviours. Internal hierarchical lists
> are not accessible anymore from developer's code. There is a memory
> separation now. This is also true for all 4D resources.

Cheers

--
David Dancy
Sydney, Australia
**********************************************************************
Live Data Mapping Services with 4D v11 SQL
See it for yourself - http://www.4d.com/solutions/ndwater.html

4D Internet Users Group (4D iNUG)
FAQ:  http://www.4D.com/support/faqnug.html
Archive:  http://lists.4D.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4D_Tech-Unsubscribe@...
**********************************************************************