>I agree with you and suggested the same for this ballot issue (235) >during the SV-EC face-to-face. Dave was of the opinion though that >there would still be a problem with dangling references. I am not sure why that would be. The most extreme case I can come up with is a static task containing fork/join_any. The subprocesses could continue to access the ref argument after the task returns, so the reference must still be considered valid and prevent garbage collection. If an implementation didn't want to have to keep track of whether there were any such active subprocesses in a static task, a static ref formal would have to be treated as a valid reference until overwritten by another call. That could defer garbage collection unnecessarily, but that would be an implementation choice not inherent in the language. Since SV allows declaring static objects in automatic tasks, is it sufficient to forbid ref arguments in static tasks? Is it possible to declare a ref argument formal to be static in an automatic task? Steven Sharp sharp@cadence.comReceived on Fri Apr 8 13:55:42 2005
This archive was generated by hypermail 2.1.8 : Fri Apr 08 2005 - 13:55:53 PDT