WPC zߠ\\ h7i},y+YeAF~k_n zW1n񞶷н,Oɭ~1OrI* ({d]m8rnzt;9)0muCK+M\,ᒎ_/[ Ϊ&8; o私JSͷ+Ei"SK*mڰlxt/B׿Q9Fz|N50{=n Qԭ)dݐo_D96NM:PXAAZ˿=J3f+4?ۂs2 AoKn~>֋rmXDN ^tIX,=[1k!^y8N$K>낓+U\S"8n$>>  3   ,X>>>(#F>#FF# FX3J3/96-073#F /#FF#>F#Ԉ X X3J3ANSIFortranStandardsCommittee>(#CraigT.Dedo T JORItemsonMinorI/OEnhancements=(#April26,1996  eee(#Page  1  ڀof109LXp>New Century Schoolbook Bold PerDU  ,X.< ,D:\X3J3\JOR\96-073.WPD<D:\X3J3\JOR\96-073.WPD/  (3ǝ$ !XX  NNN    3  3|xJOR Items on Minor I/O EnhancementsReport,' ' X3J3/96-073$Craig T. Dedo$Craig T. Dedo .   /4 Fortran 2000 Standard+None     "1 302Original    '  >>>  3   ,X>>>(#F>#FF#FX3J3/96-073#F /#FF#>F#Ԉ X X3J3ANSIFortranStandardsCommittee>(#CraigT.Dedo T JORItemsonMinorI/OEnhancements=(#April26,1996  eee(#Page  1  ڀof102p`4New Century Schoolbook2p`4New Century Schoolbook+`4New Century Schoolbook2p`4New Century Schoolbook+`4New Century Schoolbook9LXp>New Century Schoolbook Bold9LXp>New Century Schoolbook BoldH2p`4New Century Schoolbook+`4New Century Schoolbook9LXp>New Century Schoolbook Bold !XX  >>>    3      r^4` <hDp Lx !(#T$%&XrӜ>>%  %  %  %  @  JORItemsonMinorI/OEnhancements ]  @SS"byCraigT.Dedo@#April26,1996  ThisreportcontainsproposalsforminortechnicalenhancementsintheareaofI/O.IpresentedmostoftheseideasinemailtoX3J3onNovember17,1994andNovember30,1994.IamresubmittingtheseideasnowsothattheyareeligibleforinclusioninFortran2000.  Iamrecommendingthemmostlyforreasonsofprogrammingeffectiveness.IbelievethatFortranshould,tothegreatestextentpossible,beinternallyconsistentandsimpletouse.Fortranshouldnothavethesortofirregularities,commoninotherlanguages,whichareusuallyknownonlytothewellinitiated.Suchirregularitiesaretrapsand"gotcha"sthatmakelifeneedlesslydifficultfortheapplicationprogrammers,whoareour customers.  E  #>># `   d   `   ~!   ����4 � ����` � ���� �UseoftheSIZE=Keyword�� � �; � �<KEYWORDS> ���� ��� � � � �<STATUS> ����` � ���� �Registered�� � �X� �<TARGET> ����` � ���� ��� � �r� �<SUBGROUP> ���� ��� � �/� �<VERSION> ����` � ���� �1�� � �� �<REQUIREMENT> ���� �AllowtheuseoftheSIZE=specifierforbothadvancingandnonadvancingI/O.</REQUIREMENT><JUSTIFICATION> ���� �Fortran90allowstheuseoftheSIZE=specifieronlyfornonadvancingI/O.InformalconversationsatX3J3meetingsin1994suggestedthatthedevelopersoftheFortran90standardthoughtthatitwouldbeusefulmainlyfornonadvancingI/O.Thisisundulyrestrictive;usersshouldbeabletousetheSIZE=specifierbothinadvancingandnonadvancingI/O.</JUSTIFICATION><SUGGESTEDIMPLEMENTATION> ���� �Thiscouldbeaccomplishedbymakingminoreditstosections9.2.1.3.1,9.4.1,and9.4.1.9.</SUGGESTEDIMPLEMENTATION><ESTIMATEDIMPACT> ���� �Minimal.ManyFortrancompilersalreadyhavesomeothermethodforobtainingthesizeoftherecordwhenusingadvancingI/O.</ESTIMATEDIMPACT><SUBMITTEDBY> ���� �CraigT.Dedo ���� �ElmbrookComputerServices ���� �17130W.BurleighPlace ���� �Brookfield,WI53005 ���� �(414)783-5869 ���� �Email: ����` �Craig.Dedo@mixcom.com�� � �+;%2� �</SUBMITTEDBY><REFERENCE> ���� �X3J3/96007r09.2.1.3.1,9.4.1,9.4.1.9�� � �./(6� �</REFERENCE><HISTORY><EVENT> ����4 � ����` �May1996,meeting137: ���� �submitted���96-073��� � �7� �</HISTORY></FORTREQ>**********************************************************************************************<FORTREQ> ����` � ���� ��� � � +� �<NUMBER> ����` � ���� ��� � �E � �<TITLE> ����4 � ����` � ���� �InternalFileDataType�� � �  � �<KEYWORDS> ���� ��� � � b � �<STATUS> ����` � ���� �Registered�� � �| � �<TARGET> ����` � ���� ��� � �9 � �<SUBGROUP> ���� ��� � � � �<VERSION> ����` � ���� �1�� � �V � �<REQUIREMENT> ���� �AllowthedataobjectsofanyKINDofCHARACTERdatatypethatisdefinedontheprocessortobeusedasinternalfiles.</REQUIREMENT><JUSTIFICATION> ���� �Fortran90requiresthatinternalfilesmustbeofdefaultCHARACTERtype.Thisisanunnecessaryrestriction.Inthenext1012years(i.e.,theexpectedusefullifeoftheFortran2000standard),IexpectthattheuseofmultibytecharactersetssuchasUnicode(a.k.a.ISO10646)willgrowtobeofsubstantialimportanceincharactermanipulation.Fortranshouldanticipatethisdevelopmentandbepreparedtohandleit.Inaddition,notallowingall�KINDs�ofcharactervariablesasinternalfilescreatesanirregularity.</JUSTIFICATION><SUGGESTEDIMPLEMENTATION> ���� �Thiscouldbeaccomplishedbymakingminoreditstosections9.2.2.1,9.3,and9.4.2.</SUGGESTEDIMPLEMENTATION><ESTIMATEDIMPACT> ���� �Minimal.AnyFortranprocessorwhichsupportsdifferentKINDsofCHARACTERdatatypesalreadyhastodealwithissuessuchasrepresentationandtranslation.</ESTIMATEDIMPACT><SUBMITTEDBY> ���� �CraigT.Dedo ���� �ElmbrookComputerServices ���� �17130W.BurleighPlace ���� �Brookfield,WI53005 ���� �(414)783-5869 ���� �Email: ����` �Craig.Dedo@mixcom.com�� � �'9!-� �</SUBMITTEDBY><REFERENCE> ���� �X3J3/96007r09.2.2.1,9.3,9.4.2</REFERENCE><HISTORY><EVENT> ����4 � ����` �May1996,meeting137: ���� �submitted���96-073��� � �~-!'5� �</HISTORY></FORTREQ>�� � �.(7� �**********************************************************************************************<FORTREQ> ����` � ���� ��� � ��� �<NUMBER> ����` � ���� ��� � �z� �<TITLE> ����4 � ����` � ���� �InternalFilesandListDirectedFormatting�� � �7� �<KEYWORDS> ���� ��� � �Q � �<STATUS> ����` � ���� �Registered�� � � � �<TARGET> ����` � ���� ��� � � n� �<SUBGROUP> ���� ��� � � +� �<VERSION> ����` � ���� �1�� � �E � �<REQUIREMENT> ���� �AddanotetothestandardwhichexplicitlystatesthatstartingwithFortran90,itispermittedtodolistdirectedI/Ooninternalfiles.</REQUIREMENT><JUSTIFICATION> ���� �AfrequentlyaskedquestionaboutFortran90iswhetheritispermittedtoperformlistdirectedI/Ooninternalfiles.FORTRAN77didnotpermitthispractice,butFortran90removedthisrestriction.Unfortunately,thefrequencyofthequestionindicatesthatmanyusersstilldoubtwhetherthisispermitted.Anoteinthestandardshouldmakethispointclear.</JUSTIFICATION><SUGGESTEDIMPLEMENTATION> ���� �Createanoteattheendofsection9.2.2.2whichwouldreadsomethingalongthelinesof,"StartingwithFortran90,itispermissibletoperformlistdirectedI/Ooninternalfiles."</SUGGESTEDIMPLEMENTATION><ESTIMATEDIMPACT> ���� �None.Thisismostlyaneditorialmatter.Somevendorsmaywishtochangetheirdocumentation.</ESTIMATEDIMPACT><SUBMITTEDBY> ���� �CraigT.Dedo ���� �ElmbrookComputerServices ���� �17130W.BurleighPlace ���� �Brookfield,WI53005 ���� �(414)783-5869 ���� �Email: ����` �Craig.Dedo@mixcom.com�� � �!Q%� �</SUBMITTEDBY><REFERENCE> ���� �X3J3/96007r09.2.2.2</REFERENCE><HISTORY><EVENT> ����4 � ����` �May1996,meeting137: ���� �submitted���96-073��� � �'9!-� �</HISTORY></FORTREQ>**********************************************************************************************<FORTREQ> ����` � ���� ��� � �*-$1� �<NUMBER> ����` � ���� ��� � �G+$2� �<TITLE> ����4 � ����` � ���� �NamedScratchFiles�� � �,%3� �<KEYWORDS> ���� ��� � �,d&4� �<STATUS> ����` � ���� �Registered�� � �~-!'5� �<TARGET> ����` � ���� ��� � �;.'6� �<SUBGROUP> ���� ��� � �.(7� �<VERSION> ����` � ���� �1�� � �]���� �<REQUIREMENT> ���� �AllowtheusertospecifyafilenameifafileisopenedwithSTATUS="SCRATCH".</REQUIREMENT><JUSTIFICATION> ���� �Fortran90doesnotallowtheusertonamescratchfiles.Weshouldliftthisrestriction.Allowingtheprogrammertonamescratchfilescanbeuseful,especiallyiftheprogramcrashes.Notallowingtheprogrammertonameafileinthisonecaseisanunnecessaryirregularity.��sSince�thereislegacycodewhichhasSTATUS="SCRATCH"withoutaFILE=specifier,thebestsolutionistoallowtheoptionaluseofFILE=withSTATUS="SCRATCH".</JUSTIFICATION><SUGGESTEDIMPLEMENTATION> ���� �Thiscouldbeaccomplishedbymakingminorchangestosection9.3.4.</SUGGESTEDIMPLEMENTATION><ESTIMATEDIMPACT> ���� �Minimal.Addingthiscapabilityshouldnotbeverydifficulttoimplement.</ESTIMATEDIMPACT><SUBMITTEDBY> ���� �CraigT.Dedo ���� �ElmbrookComputerServices ���� �17130W.BurleighPlace ���� �Brookfield,WI53005 ���� �(414)783-5869 ���� �Email: ����` �Craig.Dedo@mixcom.com�� � � � �</SUBMITTEDBY><REFERENCE> ���� �X3J3/96007r09.2.2.2</REFERENCE><HISTORY><EVENT> ����4 � ����` �May1996,meeting137: ���� �submitted��96-073��� � � $� �</HISTORY></FORTREQ>**********************************************************************************************<FORTREQ> ����` � ���� ��� � �#(� �<NUMBER> ����` � ���� ��� � �$E)� �<TITLE> ����4 � ����` � ���� �BehaviorofOPENwithSTATUS="UNKNOWN"�� � �_%*� �<KEYWORDS> ���� ��� � �&+� �<STATUS> ����` � ���� �Registered�� � �&| ,� �<TARGET> ����` � ���� ��� � �'9!-� �<SUBGROUP> ���� ��� � �S(!.� �<VERSION> ����` � ���� �1�� � �)"/� �<REQUIREMENT> ���� �IftheOPENstatementspecifiesthatafileisopenedwithSTATUS="UNKNOWN",thestandardshouldspecifythatifthefileexists,itisopenedasifSTATUS="OLD",andifthefiledoesnotexists,itisopenedasifSTATUS="NEW".</REQUIREMENT><JUSTIFICATION>�� � �.(7� � ���� �Fortran90and95leavethisbehaviorasprocessordependent.Thisdefinitioninterfereswithportability.Italsorequirestheusertoanticipatetheprocessor'sbehaviorinsteadofrelyingonaknown,standardbehavior.Thisisanunnecessaryirregularity.TherecommendedchangetothestandardbehaviorisalreadyapopularimplementationofOPENwithSTATUS="UNKNOWN".TheDEC(VMS,Unix,andNT),IBMAIX,andLaheyFortrancompilersalreadyusethisimplementation.</JUSTIFICATION><SUGGESTEDIMPLEMENTATION> ���� �Thiscouldbeaccomplishedbymakingminorchangestosection9.3.4.2.</SUGGESTEDIMPLEMENTATION><ESTIMATEDIMPACT> ���� �Thischangeshouldnotposeanyseriousimplementationproblems.Iexpectthattheinstancesofactualincompatibilitywillbefew.Programmersshouldbeabletoeasilyresolveanysuchconflicts.Implementorsshouldbeabletoeasilyandinexpensivelychangetheirimplementationstoconformtothenewrule,whichisequivalenttothefollowingcode:CHARACTER(LEN=250) ���� �:: ���� �FILENAME�� � �- � �INTEGER ����4 �:: ����` �LUN�� � � � �LOGICAL ����4 �:: ����` �LEXIST�� � �J � �!DefinethevaluesofLUNandFILENAMEsomewherepriortoopeningthefile.INQUIRE(FILE=FILENAME,EXIST=LEXIST)IF(LEXIST)THEN ���� �OPEN(LUN,FILE=FILENAME,STATUS="OLD")ELSE ���� �OPEN(LUN,FILE=FILENAME,STATUS="NEW")ENDIF</ESTIMATEDIMPACT><SUBMITTEDBY> ���� �CraigT.Dedo ���� �ElmbrookComputerServices ���� �17130W.BurleighPlace ���� �Brookfield,WI53005 ���� �(414)783-5869 ���� �Email: ����` �Craig.Dedo@mixcom.com�� � �w"� �</SUBMITTEDBY><REFERENCE> ���� �X3J3/96007r09.3.4.2</REFERENCE><HISTORY><EVENT> ����4 � ����` �May1996,meeting137: ���� �submitted��96-073��� � �_%*� �</HISTORY></FORTREQ>**********************************************************************************************<FORTREQ> ����` � ���� ��� � �S(!.� �<NUMBER> ����` � ���� ��� � �)"/� �<TITLE> ����4 � ����` � ���� �ActionofSTATUS="REPLACE"withMultipleVersionFiles�� � �)p#0� �<KEYWORDS> ���� ��� � �*-$1� �<STATUS> ����` � ���� �Registered�� � �G+$2� �<TARGET> ����` � ���� ��� � �,%3� �<SUBGROUP> ���� ��� � �,d&4� �<VERSION> ����` � ���� �1�� � �~-!'5� �<REQUIREMENT>�� � �.(7� � ���� �Ifanoperatingsystemorfilesystemsupportsfileswithmultipleversionnumbers,openingafilewithSTATUS="REPLACE"shouldcreateanewfilewiththenextavailableversionnumberorversiondesignator.</REQUIREMENT><JUSTIFICATION> ���� �ThestandardissilentonwhatshouldhappenifafileisopenedwithSTATUS="REPLACE"andtheoperatingsystemorafilesystemsupportedbytheoperatingsystemsupportsmultipleversionfiles.Currently,theFortran95DISsays,"IfREPLACEisspecifiedandthefilesdoesexist,thefileisdeleted,anewfileiscreatedwiththesamename,andthestatusischangedtoold."Thisappearstoimplythatonasystemthatsupportsmultipleversionsoffiles,theoldversionshouldbedeletedandanemptyfilewiththesameversionnumbercreatedinitsplace.However,closeconsiderationofthetextdoesnotmakeitclearwhether: ���� �(1)theoldversionshouldbedeletedor, ���� �(2)anewfilecreatedwith�the�nextavailableversiondesignator. ���� �Hereisanexample.ThereisanexistingfileCOMPLEX_FILE.DAT;3,wherethenumberfollowingthesemicolonistheversiondesignator.AFortranprogramopensthefileusingSTATUS="REPLACE".DoestheFortranprogramdeleteCOMPLEX_FILE.DAT;3andrecreateitasempty?Or,doestheFortranprogramcreateanewversion,e.g.,COMPLEX_FILE.DAT;4? ���� �Ibelievethatthemoreusefulchoiceistocreateanewfilewiththenextavailableversiondesignator.Choosingthisoptionwouldpreservethepurposeofmultipleversionsoffiles,i.e.,tomakeiteasierforusersofallkindstorecoverfromdisastrousmistakes. ���� �Forreasonsofclarity,regularity,andportability,weshouldruleonthisissueratherthanleavingitasprocessordependent. ���� �SomemayarguethatfewoperatingsystemsorfilesystemsoffermultipleversionsoffilesrightnowandthereforethisissueisirrelevantforthevastmajorityofFortranprogrammers.Whilemultipleversionfilesystemsmaybefew,thisfeatureofafilesystemmaygreatlyincreaseinpopularityduringthelifeoftheFortran2000standard.,whichmaybeaslateas2012.Therefore,theissuemaybeveryrelevantforasignificantfractionofFortranprogrammersduringthelifeoftheFortran2000standard.</JUSTIFICATION><SUGGESTEDIMPLEMENTATION> ���� �Thiscouldbeaccomplishedbymakingminorchangestosection9.3.4.2.</SUGGESTEDIMPLEMENTATION><ESTIMATEDIMPACT> ���� �Minimal.Addingthiscapabilityshouldnotbeverydifficulttoimplement.</ESTIMATEDIMPACT><SUBMITTEDBY> ���� �CraigT.Dedo ���� �ElmbrookComputerServices ���� �17130W.BurleighPlace ���� �Brookfield,WI53005 ���� �(414)783-5869 ���� �Email: ����` �Craig.Dedo@mixcom.com�� � �G+$2� �</SUBMITTEDBY><REFERENCE> ���� �X3J3/96007r09.3.4.2</REFERENCE>�� � �.(7� �Ї<HISTORY><EVENT> ����4 � ����` �May1996,meeting137: ���� �submitted���96-073��� � ��� �</HISTORY></FORTREQ>**********************************************************************************************<FORTREQ> ����` � ���� ��� � � � �<NUMBER> ����` � ���� ��� � � n� �<TITLE> ����4 � ����` � ���� �BACKSPACEwithListDirectedandNamelistFormats�� � � +� �<KEYWORDS> ���� ��� � �E � �<STATUS> ����` � ���� �Registered�� � �  � �<TARGET> ����` � ���� ��� � � b � �<SUBGROUP> ���� ��� � �| � �<VERSION> ����` � ���� �1�� � �9 � �<REQUIREMENT> ���� �Removetherestrictionwhichprohibitsbackspacingoverrecordswrittenusinglistdirectedandnamelistformatting.</REQUIREMENT><JUSTIFICATION> ���� �Thereappearstobeverylittle,ifany,differencebetweenrecordswrittenusingformattedI/OandthoseusinglistdirectedornamelistI/O.Therefore,thisappearstobeanunnecessaryrestriction.Fortran2000shouldremovethisrestriction.</JUSTIFICATION><SUGGESTEDIMPLEMENTATION> ���� �Thiscouldbeaccomplishedbymakingminorchangestosection9.5.1</SUGGESTEDIMPLEMENTATION><ESTIMATEDIMPACT> ���� �Minimal.Addingthiscapabilityshouldnotbeverydifficulttoimplement.</ESTIMATEDIMPACT><SUBMITTEDBY> ���� �CraigT.Dedo ���� �ElmbrookComputerServices ���� �17130W.BurleighPlace ���� �Brookfield,WI53005 ���� �(414)783-5869 ���� �Email: ����` �Craig.Dedo@mixcom.com�� � �(#'� �</SUBMITTEDBY><REFERENCE> ���� �X3J3/96007r09.5.1</REFERENCE><HISTORY><EVENT> ����4 � ����` �May1996,meeting137: ���� �submitted��96-nnn��96-073��� � �)"/� �</HISTORY></FORTREQ>**********************************************************************************************<FORTREQ> ����` � ���� ��� � �,%3� �<NUMBER> ����` � ���� ��� � �,d&4� �<TITLE> ����4 � ����` � ���� �NEXTREC=SpecifierintheINQUIREStatement�� � �~-!'5� �<KEYWORDS> ���� ��� � �;.'6� �<STATUS> ����` � ���� �Registered�� � �.(7� �<TARGET> ����` � ���� ��� � �]���� �<SUBGROUP> ���� ��� � ��� �<VERSION> ����` � ���� �1�� � �z� �<REQUIREMENT> ���� �Fortran2000shouldallowtheuseoftheNEXTREC=specifierforbothdirectaccessandsequentialaccessfiles.</REQUIREMENT><JUSTIFICATION> ���� �TheFortran95DISonlyallowstheuseoftheNEXTREC=specifieronlyfordirectaccessfiles.Thisisanunnecessaryirregularity.</JUSTIFICATION><SUGGESTEDIMPLEMENTATION> ���� �Thiscouldbeaccomplishedbymakingminorchangestosection9.6.1.14</SUGGESTEDIMPLEMENTATION><ESTIMATEDIMPACT> ���� �Minimal.Addingthiscapabilityshouldnotbeverydifficulttoimplement.</ESTIMATEDIMPACT><SUBMITTEDBY> ���� �CraigT.Dedo ���� �ElmbrookComputerServices ���� �17130W.BurleighPlace ���� �Brookfield,WI53005 ���� �(414)783-5869 ���� �Email: ����` �Craig.Dedo@mixcom.com�� � � � �</SUBMITTEDBY><REFERENCE> ���� �X3J3/96007r09.6.1.14</REFERENCE><HISTORY><EVENT> ����4 � ����` �May1996,meeting137: ���� �submitted��96-nnn��96-073��� � � $� �</HISTORY></FORTREQ>**********************************************************************************************<FORTREQ> ����` � ���� ��� � �#(� �<NUMBER> ����` � ���� ��� � �$E)� �<TITLE> ����4 � ����` � ���� �ADVANCE="NO"SpecifierandPrompting�� � �_%*� �<KEYWORDS> ���� ��� � �&+� �<STATUS> ����` � ���� �Registered�� � �&| ,� �<TARGET> ����` � ���� ��� � �'9!-� �<SUBGROUP> ���� ��� � �S(!.� �<VERSION> ����` � ���� �1�� � �)"/� �<REQUIREMENT> ���� �Fortran2000shouldguaranteethattheuseoftheADVANCE="NO"specifierinI/Ostatementscanbeusedbyprogrammerstoimplementagenuinepromptingcapability.</REQUIREMENT> ���� �<JUSTIFICATION>�� � �;.'6� � ���� �InterpretationsoftheFortran90standardindicatethattheoftheADVANCE="NO"specifierin ���� �I/OstatementsdoesnotguaranteethatprogrammerscanuseacombinationofsuchI/Ostatementsinordertoimplementagenuinepromptingcapability. ���� �ItismybeliefthatmostusersexpectADVANCE="NO"I/Ostatementstoprovideapromptingcapability.Thisdifferencecreatesagapbetweenwhatusersexpectandwhatthecurrentstandardactuallyprovides.TheexistenceofthisgapcontributestotheimagethatFortranhasofbeinga"StoneAge"relic.Thissituationshouldbecorrected. ���� �Althoughthegrowingpopularityofwindowingsystemsreducestheseverityofthisgap,IexpectthataneedforagenuinepromptingcapabilitywillexistforthelifeofFortran2000.</JUSTIFICATION><SUGGESTEDIMPLEMENTATION> ���� �Thiscouldbeaccomplishedbymakingminorchangestosections9.2.1.3.1and9.4.1.8.</SUGGESTEDIMPLEMENTATION><ESTIMATEDIMPACT> ���� �Minimal.Addingthiscapabilityshouldnotbeverydifficulttoimplement.</ESTIMATEDIMPACT><SUBMITTEDBY> ���� �CraigT.Dedo ���� �ElmbrookComputerServices ���� �17130W.BurleighPlace ���� �Brookfield,WI53005 ���� �(414)783-5869 ���� �Email: ����` �Craig.Dedo@mixcom.com�� � �L� �</SUBMITTEDBY><REFERENCE> ���� �X3J3/96007r09.2.1.3.1,9.4.1.8</REFERENCE><HISTORY><EVENT> ����4 � ����` �May1996,meeting137: ���� �submitted��96-nnn��96-073��� � �4 #� �</HISTORY></FORTREQ>**********************************************************************************************<FORTREQ> ����` � ���� ��� � �(#'� �<NUMBER> ����` � ���� ��� � �#(� �<TITLE> ����4 � ����` � ���� �EditorialChangesforChapter9�� � �$E)� �<KEYWORDS> ���� ��� � �_%*� �<STATUS> ����` � ���� �Registered�� � �&+� �<TARGET> ����` � ���� ��� � �&| ,� �<SUBGROUP> ���� ��� � �'9!-� �<VERSION> ����` � ���� �1�� � �S(!.� �<REQUIREMENT> ���� �Fortran2000shouldincludeanyoftheeditorialchangestoChapter9thatIrecommendedinmypaper94-375attheNovemberof1994meetingofX3J3,andwhichdidnotmakeitintoFortran95.ManyofthesechangeswerenotincludedinFortran95duetotheheavyscheduleofothereditorialworkthathadtobedoneinordertokeepFortran95onschedule.</REQUIREMENT><JUSTIFICATION>�� � �.(7� � ���� �IrecommendedtheseeditorialchangesinordertomakeChapter9amuchmorecoherentandwellorganizedpartofthedocument.MakingthesechangeswouldmakeChapter9muchmorereadableandeasiertouse.</JUSTIFICATION><SUGGESTEDIMPLEMENTATION> ���� �ThiscouldbeaccomplishedbymakingtherecommendedchangesthroughoutChapter9.</SUGGESTEDIMPLEMENTATION><ESTIMATEDIMPACT> ���� �TherewouldbenoimpactonthetechnicalcontentofFortran2000.Therecouldbemoderatetoextensiveeditorialworkrequired.X3J3shouldasktheFortran2000ProjectEditortoprovideanestimateoftheimpact. ���� �SincesomeoftherecommendationsreorganizesubsectionsofChapter9,itwouldbenecessarytocheckotherpartsofthedocumenttoseeifcrossreferencestothereorganizedpartsneedtobechanged.</ESTIMATEDIMPACT><SUBMITTEDBY> ���� �CraigT.Dedo ���� �ElmbrookComputerServices ���� �17130W.BurleighPlace ���� �Brookfield,WI53005 ���� �(414)783-5869 ���� �Email: ����` �Craig.Dedo@mixcom.com�� � �u� �</SUBMITTEDBY><REFERENCE> ���� �X3J3/94-375,"EditorialChangesfor�007r3�Chapter9"</REFERENCE><HISTORY><EVENT> ����4 � ����` �May1996,meeting137: ���� �submitted��96-nnn��96-073��� � �]!� �</HISTORY></FORTREQ>[Endof96�-0�0b73�]