Re: Tetris and javascript

Subject: Re: Tetris and javascript

From: Edward Brown <email@hidden>

Date: Mon, 23 May 2005 20:41:46 +0100

Delivered-to: email@hidden

Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:mime-version:in-reply-to:references:content-type:message-id:from:subject:date:to:x-mailer; b=YAsC35tbXVRLjyw15WhxYwKISLZ6brdLM6zJQclcBI4d30ytslfzq9EKJ5lpsyw+lMuuP0Yy3ns05l3mDfQ1EB1joBwKSORSJxjVH5qJsmIYkVKYEvl7U3f5i1WA6XHl7QYWu9ragdyhrzSdQQjTtmz5agIvUgRcMDEG7a84vBc=

On 23 May 2005, at 19:12, Pierre-Olivier Latour wrote:

So far, we found two bugs in _javascript_:

2) _javascript_s may corrupt memory when writing more than once to the same output e.g.

This is really useful. I've amended my composition to not do this (was only doing it in a couple of places anyway) and it made no difference :-(. However, taking your information as a starting point I figured that making many changes to a variable taken from an output could trigger the same problem:

(at startup)

myArray = new array

outputs[2]=myArray

(normal processing)

myArray = outputs[2]

outputs[2]=myArray

Changing to this structure:

(normal processing)

tmpArray = new array

for (a=0;a<n;a++) myArray[a]=tmpArray[a]

outputs[2]=myArray

has made my composition really stable. So I'm going to spend a bit more time on it and post to quartzcomps. Thanks again for the bug hints!

Edward

_______________________________________________ Do not post admin requests to the list. They will be ignored. Quartzcomposer-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/quartzcomposer-dev/email@hidden This email sent to email@hidden

References:

>Tetris and javascript (From: Will Thimbleby <email@hidden>)

>Re: Tetris and javascript (From: Edward Brown <email@hidden>)

>Re: Tetris and javascript (From: Pierre-Olivier Latour <email@hidden>)