J3/14-162 To: J3 From: Van Snyder Subject: Even more editorial (?) stuff. Date: 2014 May 30 Edits with respect to 14-007r1 ------------------------------ [19:30 1.3.149.6] Replace "clause" with "". [19:43 1.3.149.10] Replace "clause" with "". [34:1 2.3.2p1] Replace "clause" with "subclause". [70:5,7 4.5.4.2p1] Replace "clause" with "" twice. [70:10,11 4.5.4.3p1] Replace "clause" with "" twice. [100:8-9] Delete C547, which is overkill because the associated actual argument is covered by C1303, C1304, and 16.6.7 "Variable definition context." [129:8 C642] There is a cross reference to type LOCK_TYPE in C643, but none to C_PTR or C_FUNPTR in C642 or C643. If one is needed at all, it's only needed in C642. Insert "(15.3.3)" after "C_PTR" and "C_FUNPTR" -- or delete "(13.8.2.16)" at [129:9]. [213:31 C929] Insert "exponent" after "decimal" for consistency with numerous other places (e.g., [382:1]) where the same concept is required. [312:9 12.6.2.6p7] Replace "clause" with "suffix". [312:12 12.6.2.6p8] Replace "clause" with "suffix". [386:17 13.7.145p5] It's not obvious what "this result is within range" means. "Within range" of what? Replace "this result is within range; if not" with "$X = 0$ or TINY(X) $\leq | X \times b^I | \leq$ HUGE(X); otherwise". [388:20,22,23,25 13.7.149p7] Before "exponent" insert "decimal" four times, so as to avoid any confusion that the exponent might be in radix RADIX. [402:25 C1303] Insert "in an ALLOCATE statement without a SOURCE= specifier, as an in a DEALLOCATE statement" after "" for consistency with C602 on EVENT_TYPE in TS 18508. {Does this instead need an interp? Does it need to be in the incompatibility list in 1.6.3?} [402:26,29 C1303, C1304] Replace "where" with "if" twice. [402:27 C1304] Insert "in an ALLOCATE statement without a SOURCE= specifier, as an in a DEALLOCATE statement" after "" for consistency with C603 on EVENT_TYPE in TS 18508. {Does this instead need an interp? Does it need to be in the incompatibility list in 1.6.3?} [402:29+ C1304+ 13.8.2.16] To improve on the protection in C435, insert a paragraph "The value of the actual argument associated with the CPTR argument of the C_F_POINTER subroutine from the ISO_C_BINDING intrinsic module shall not be the address of a variable of type LOCK_TYPE." {Should this be a feature request? Does this need to be added to the intro and/or compatibility subclause?} [419:9,11,12,13 14.11.18p6] Before "exponent" insert "decimal" four times, so as to avoid any confusion that the exponent might be in radix RADIX. [461:18-19 16.3.3p1] Replace "clause" with "suffix" twice.