RE: [sv-ec] Mantis 2606 - type name resolution in out-of-block method prototypes

From: Francoise Martinolle <fm_at_.....>
Date: Mon Jun 08 2009 - 18:45:48 PDT
 

I read the proposal. I am not clear as how  to resolve an identifier
found 
in the method body, should one first try to resolve the identifier in
the class declaration, then if not found, 
follow the normal simple name resolution rules.
I think it can be interpreted that way but perhaps we should be more
precise and say that.

From the proposal, I cannot determine which T the following example
resolves to:

class c;
typedef  int T;
extern task tf;

endclass

typedef real T;

task tf;
  T arg1;
  begin
  end
endtask

Rather than saying that the Out of block method declaration has access
to class properties and types 
I would prefer saying that resolving identifier in the the method body
is as if the method body was placed at the end of the class declaration.
Consequently any declaration between the endclass
and the task method body has no effect.

Francoise
    '
-----Original Message-----
From: owner-sv-ec@eda.org [mailto:owner-sv-ec@eda.org] On Behalf Of
Gordon Vreugdenhil
Sent: Monday, June 08, 2009 5:11 PM
To: SV_EC List
Subject: [sv-ec] Mantis 2606 - type name resolution in out-of-block
method prototypes

I've uploaded a proposal for 2606 (in Word and pdf) that addresses the
direct ballot question.  It doesn't address a couple of the other issues
raised in the meeting today but is likely as much as we can do for this
PAR.  I think this captures the consensus at least in intent.

I am not available from June 10-16 so someone else can pick up the word
doc and make any additional changes if this isn't adequate.

Gord.
--
--------------------------------------------------------------------
Gordon Vreugdenhil                                503-685-0808
Model Technology (Mentor Graphics)                gordonv@model.com


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Received on Mon, 8 Jun 2009 21:45:48 -0400

This archive was generated by hypermail 2.1.8 : Mon Jun 08 2009 - 18:47:39 PDT