Small kjs value reference patch

[porten at froglogic.com]

On Tue, 4 Nov 2003, Zack Rusin wrote:

> increment reference count on the copying object before dereferencing the
> currently held value. It's more for the semantic than technical
> correctness as to invoke a bug a collector would have to be invoked at
> the same time as the copying value is getting out of scope and the
> oprator= with it is called. Possible only in a multithreaded app with a
> funky synchronization, but in any way it doesn't uglify the code and
> seems more natural for people who are used to exceptions. Problems?

Looks okay to me.

Harri.