From listadm Mon Sep 16 16:11:17 2002 Received: from email1.ansi.org (email1.ansi.org [12.15.192.17]) by dkuug.dk (8.9.2/8.9.2) with ESMTP id QAA71879 for ; Mon, 16 Sep 2002 16:11:16 +0200 (CEST) (envelope-from mdeane@ANSI.org) Received: by email1.ansi.org with Internet Mail Service (5.5.2653.19) id ; Mon, 16 Sep 2002 10:12:53 -0400 Message-ID: <2F81C8110D55D411882A0020356797B2027FD91E@email1.ansi.org> From: Matthew Deane To: "'SC 22 Distribution List'" Subject: SC 22 N 3494 - Summary of Voting on SC 22 N 3408, Registration an d Approval Ballot for PDTR 19755 Date: Mon, 16 Sep 2002 10:12:51 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C25D8B.24BEDA40" This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C25D8B.24BEDA40 Content-Type: text/plain; charset="iso-8859-1" ISO/IEC JTC 1/SC22 Programming languages, their environments and system software interfaces Secretariat: U.S.A. (ANSI) ISO/IEC JTC 1/SC22 N3494 TITLE: Summary of Voting on SC 22 N 3408, Registration and Approval Ballot for PDTR 19755, Object finalization for programming language COBOL (Type 2 TR) DATE ASSIGNED: 2002-09-16 SOURCE: SC 22 Secretariat BACKWARD POINTER: N/A DOCUMENT TYPE: Summary of Voting PROJECT NUMBER: 22.01.07.01 STATUS: Per the results of this ballot, the registration and approval of the PDTR is approved. The NB ballot comments were sent to the WG 4 Convenor for review at their recent meeting. WG 4 is instructed to send the text for DTR ballot and a disposition of comments report to the SC 22 Secretariat for further processing. ACTION IDENTIFIER: ACT DUE DATE: DISTRIBUTION: Text CROSS REFERENCE: SC 22 N3408 DISTRIBUTION FORM: Def Address reply to: ISO/IEC JTC 1/SC22 Secretariat Matt Deane ANSI 25 West 43rd Street New York, NY 10036 Telephone: (212) 642-4992 Fax: (212) 840-2298 Email: mdeane@ansi.org ___end cover page, beginning of summary of voting________ SUMMARY OF VOTING ON Letter Ballot Reference No: SC22 N3408 Circulated by: JTC 1/SC22 Circulation Date: 2002-06-06 Closing Date: 2002-09-07 SUBJECT: Summary of Voting on SC 22 N 3408, Registration Ballot for PDTR 19755, Object finalization for programming language COBOL (Type 2 TR) ---------------------------------------------------------------------- The following responses have been received on the subject of PDTR registration: "P" Members supporting registration without comment 8 (China, Denmark, Japan, Republic of Korea, Netherlands, Norway, UK, USA) "P" Members supporting registration with comments 1 (Germany) "P" Members not supporting registration - "P" Members abstaining 3 (Austria, Canada, Switzerland) "P" Members not voting 11 (Belgium, Brazil, Czech Republic, Egypt, Finland, Ireland, DPR of Korea, Romania, Russian Federation, Slovenia, Ukraine) SUMMARY OF VOTING ON Letter Ballot Reference No: SC22 N3408 Circulated by: JTC 1/SC22 Circulation Date: 2002-06-06 Closing Date: 2002-09-07 SUBJECT: Summary of Voting on SC 22 N 3408, Approval Ballot for PDTR 19755, Object finalization for programming language COBOL (Type 2 TR) ---------------------------------------------------------------------- The following responses have been received on the subject of PDTR approval: "P" Members supporting approval without comment 6 (China, Denmark, Republic of Korea, Netherlands, Norway, UK) "P" Members supporting approval with comments 3 (Germany, Japan, USA) "P" Members not supporting approval - "P" Members abstaining 3 (Austria, Canada, Switzerland) "P" Members not voting 11 (Belgium, Brazil, Czech Republic, Egypt, Finland, Ireland, DPR of Korea, Romania, Russian Federation, Slovenia, Ukraine) NB Comments Germany We have the following comments on this technical report that should be solved: Finalization of Factory objects is not yet allowed. This should not only be mentioned in annex B3 as unresolved technical issue but should be a syntax rule in 11.6a AUTO-METHOD Paragraph, saying that this paragraph is only allowed within the OBJECT part of a Class. On page 11 B.4: We understand this issue but we do not understand what is unresolved with it, and that gives us some irritation. Japan [Technical] 1. There should be a rule that says that the definition of the auto-method finalizer shall be specified only once in a class definition. 2. Page 8, 6.7, Changes to 16, Standard classes, [a]. Since INVOKEFINALIZERS method is intended to trigger resource r eclamation, rules for this method should mention reclamation. Making objects unreachable does not mean they will be reclaimed promptly. 3. Page 11, Annex B.3, Finalizers in factory object. Although it says "This proposed draft Technical Report does not provide a facility to specify a finalizer in the factory definition of a class.", no rule prohibits specifying a finalizer in the factory definition. A rule should be added for this prohibition. USA (1) We would like to see the document address more fully the problems associated with asynchronicity with regards to finalization ; (2) We would like to see further progress in the resolution of the unresolved issues in Annex B. ------_=_NextPart_001_01C25D8B.24BEDA40 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable SC 22 N 3494 - Summary of Voting on SC 22 N 3408, Registration = and Approval Ballot for PDTR 19755

ISO/IEC JTC 1/SC22
Programming languages, their = environments and system software interfaces
Secretariat:  U.S.A.  = (ANSI)
 
ISO/IEC JTC 1/SC22 N3494
 
TITLE:
Summary of Voting on SC 22 N = 3408, Registration and Approval Ballot for PDTR 19755, Object
finalization for programming = language COBOL (Type 2 TR)

DATE ASSIGNED:
2002-09-16
 
SOURCE:
SC 22 Secretariat

BACKWARD POINTER:
N/A
 
DOCUMENT TYPE:
Summary of Voting

PROJECT NUMBER:
22.01.07.01
 
STATUS:
Per the results of this ballot, = the registration and approval of the PDTR is approved.  The NB = ballot comments were sent to the WG 4 Convenor for review at their = recent meeting.  WG 4 is instructed to send the text for DTR = ballot and a disposition of comments report to the SC 22 Secretariat = for further processing.

ACTION IDENTIFIER:
ACT
 
DUE DATE:
 
DISTRIBUTION:
Text

CROSS REFERENCE:
SC 22 N3408
 
DISTRIBUTION FORM:
Def
 
Address reply to:
ISO/IEC JTC 1/SC22 = Secretariat
Matt Deane
ANSI
25 West 43rd Street
New York, NY  10036
Telephone:  (212) = 642-4992
Fax:          &nb= sp;  (212) 840-2298
Email:  = mdeane@ansi.org


___end cover page, beginning of = summary of voting________



SUMMARY OF VOTING ON


Letter Ballot Reference No: = SC22 N3408
Circulated = by:           &nb= sp;   JTC 1/SC22
Circulation = Date:            = 2002-06-06
Closing = Date:           &= nbsp;    2002-09-07

SUBJECT:  Summary of Voting = on SC 22 N 3408, Registration Ballot for PDTR 19755, Object
finalization for programming = language COBOL (Type 2 TR)
-------------------------------------------------------------------= ---

The following responses have = been received on the subject of PDTR
registration:


"P" Members supporting = registration without = comment           = ;       

8 (China, Denmark, Japan, = Republic of Korea, Netherlands, Norway, UK, USA)

"P" Members supporting = registration with = comments          &nbs= p;  

1 = (Germany)       

"P" Members not = supporting registration     

-

"P" Members = abstaining          &n= bsp;        

3 (Austria, Canada, = Switzerland)

"P" Members not = voting           =         

11 (Belgium, Brazil, Czech = Republic, Egypt, Finland, Ireland, DPR of Korea, Romania, Russian = Federation, Slovenia, Ukraine)




SUMMARY OF VOTING ON


Letter Ballot Reference = No:  SC22 N3408
Circulated = by:           &nb= sp;   JTC 1/SC22
Circulation = Date:            = 2002-06-06
Closing = Date:           &= nbsp;    2002-09-07

SUBJECT:  Summary of Voting = on SC 22 N 3408, Approval Ballot for PDTR 19755, Object
finalization for programming = language COBOL (Type 2 TR)
-------------------------------------------------------------------= ---

The following responses have = been received on the subject of PDTR
approval:


"P" Members supporting = approval without = comment           = ;       

6 (China, Denmark, Republic of = Korea, Netherlands, Norway, UK)

"P" Members supporting = approval with = comments          &nbs= p;  

3 (Germany, Japan, = USA)       

"P" Members not = supporting approval      

-

"P" Members = abstaining          &n= bsp;        

3 (Austria, Canada, = Switzerland)

"P" Members not = voting           =         

11 (Belgium, Brazil, Czech = Republic, Egypt, Finland, Ireland, DPR of Korea, Romania, Russian = Federation, Slovenia, Ukraine)


NB Comments

Germany
We have the following = comments on this technical report that should be solved:

Finalization of Factory = objects is not yet allowed. This should not only be mentioned in annex = B3 as unresolved technical issue but should be a syntax rule in 11.6a = AUTO-METHOD Paragraph, saying that this paragraph is only allowed = within the OBJECT part of a Class.

On  page 11 B.4: We = understand this issue but we do not understand what is unresolved with = it, and that gives us some irritation.


Japan
[Technical]
1. There should be a rule = that says that the definition of the
auto-method finalizer shall = be specified only once in a class definition.

2. Page 8, 6.7, Changes to = 16, Standard classes, [a].
Since INVOKEFINALIZERS = method is intended to trigger resource r
eclamation, rules for this = method should mention reclamation.  Making
objects unreachable does = not mean they will be reclaimed promptly.

3. Page 11, Annex B.3, = Finalizers in factory object.
Although it says "This = proposed draft Technical Report does not provide a
facility to specify a = finalizer in the factory definition of a class.",
no rule prohibits = specifying a finalizer in the factory definition.  A
rule should be added for = this prohibition.


USA
(1)     = We would like to see the document address more fully the problems = associated with asynchronicity with regards to finalization = ;

(2)     = We would like to see further progress in the resolution of the = unresolved issues in Annex B.

------_=_NextPart_001_01C25D8B.24BEDA40--