Re: [sv-bc] Current status of name resolution "to-do" work

From: Neil Korpusik <Neil.Korpusik_at_.....>
Date: Mon Nov 05 2007 - 18:39:24 PST
Attached is a copy of my unofficial notes that I took during
the name resolution meeting that we had this morning. They will
not be approved as official minutes of the meeting, but some
of you may find them useful anyway.

Neil




Gordon Vreugdenhil wrote On 11/05/07 02:11 PM,:
> Here is a short summary of name resolution work that was
> discussed in today's meeting as well as some pending
> Mantis work that I know about.
> 
> 1)  $unit ::  is for disambiguation only
> 
>      Gord to propose
> 
> 2)  rules for resolution into structs and classes in terms
>      of downwards/upwards resolution
> 
>      Agreement: no "desperate binding" after we get to a struct
>                 or class attempt that fails
> 
>      Gord to propose
> 
> 3)  tf binding rules for compilation units
> 
>      Current proposal is attached to 1809; no feedback yet.
> 
> 4)  bind -- rules to follow suggestions discussed with AC
>           -- no $unit/import refs; can only refer to names
>              that would be hierarchically visible
> 
>      Mark to propose
> 
> 5)  inline constraints -- can use "local ::" to bypass special
>      resolution rules.  Only permitted in an inline constraint.
> 
>      Arturo to propose
> 
> 6)  typedef forms for type params, interface types, and forward types
>      -- an explicit typedef is required to permit access to types
>         within a class referenced through such forms
> 
>      Gord to propose
> 
> 7)  extern method type resolution
>      -- "parameterized_class :: " shall only be used for scoping and
>         shall never denote a default specialization.
>      -- "parameterized_class :: " shall be required for an extern function
>         body declaration return type to name a type in the class
>      -- "parameterized_class :: " shall only be legal within the parameterized
>         class or an extern method
> 
>      Gord to propose
> 
> 8)  forward typedefs to parameterized classes shall be legal.
>      -- no definite agreement yet on whether such a forward would
>         require an explicit specialization for the default type;
>         Gord and Mark to post some examples for discussion.
> 
>      Mark to propose
> 
> 
> All - try to add "related" links to Mantis 2109 to track issues.
> 
> 
> Thanks to all for a very productive meeting.
> 
> 
> Please follow-up with any clarifications, corrections, etc.
> 
> Gord.

-- 
---------------------------------------------------------------------
Neil Korpusik                                     Tel: 408-276-6385
Frontend Technologies (FTAP)                      Fax: 408-276-5092
Sun Microsystems                       email: neil.korpusik@sun.com
---------------------------------------------------------------------


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Received on Mon Nov 5 18:39:44 2007

This archive was generated by hypermail 2.1.8 : Mon Nov 05 2007 - 18:39:57 PST