Subject: RE: [sv-cc] SV-CC LRM Version 0.8
From: Francoise Martinolle (fm@cadence.com)
Date: Tue Apr 01 2003 - 10:15:13 PST
Wording is good.
Should we say anything about what happens if calling export function and
not setting
the correct context?
Is it a runtime error, is it unspecified...
At 08:40 AM 4/1/2003 -0800, Warmke, Doug wrote:
>Francoise,
>
>Nice review comments.
>I have a response to your comment on the
>context function "transitive" property.
>
>
>
>Section A.8.2:
>I have a technical issue with the following sentence:
>
>Note that context is transitive through imported and export context
>functions. That is, if an imported function
>is running in a certain context, and if it in turn calls an exported
>function, the exported function will inherit the
>context from the imported function.
>
>Are we saying that the context brought by the import function gets
>passed to the export
>function? But what about if the export function declarative context was
>different that the context
>of the import function? Is the export call going to work?
>Shouldn't we say that before calling the export function, one must
>change the context to be
>the context of the export function?
>It looks like the way we say it, it is okay behaviour. I don't think it
>is.
>
>DOUG: The original sentence assumes that the imported and exported
>functions are declared in the same scope. We should clarify that
>to avoid miscommunicating here. How about this:
>
>"Note that context is transitive through imported and export context
>functions declared in the same scope. That is, if an imported function
>is running in a certain context, and it in turn calls an exported
>function that is available in the same context, the exported function
>can be called without any use of svSetScope()."
>
>I'm open to other rewordings as well.
>
>Regards,
>Doug
This archive was generated by hypermail 2b28 : Tue Apr 01 2003 - 10:15:45 PST