rem:            didTruncate.value = !didTruncate.value; 
context: function EditorExecuteScript(fileSpec){  fileSpec.openStreamForReading();  var buf         = { value:null };  var tmpBuf      = { value:null };  var didTruncate = { value:false };  // Log files can be quite huge, so read in a line  // at a time and execute it:  while (!fileSpec.eof())  {    buf.value         = "";    didTruncate.value = true;    // Keep looping until we get a complete line of    // text, or we hit the end of file:    while (didTruncate.value && !fileSpec.eof())    {      didTruncate.value = false;      fileSpec.readLine(tmpBuf, 1024, didTruncate);      buf.value += tmpBuf.value;      // XXX Need to null out tmpBuf.value to avoid crashing      // XXX in some JavaScript string allocation method.      // XXX This is probably leaking the buffer allocated      // XXX by the readLine() implementation.      tmpBuf.value = null;      // XXX There is a bug in the nsIFileSpec implementation.      // XXX the didTruncate value actually returns a bool      // XXX that indicates if the read successfully read      // XXX a line that fit into the buffer.      // XXX That is, it returns true if everything fit      // XXX and false if it didn't ... the reverse of what      // XXX the args name suggests.      // XXX      // XXX Remove the following line when this bug gets fixed.      didTruncate.value = !didTruncate.value;    }    eval(buf.value);  }  buf.value = null;}
meta: 9421	/local1/tlutelli/issta_data/temp/all_js/javascript/2006_temp/2006/9421/a7c2ae743d9f3b16db070d195407fb0a13808435/EditorCommands.js/buggy/editor/ui/composer/content/EditorCommands.js