This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
I am having some difficulty with this proposal; perhaps because I am ignorant on the format of the F2003 intrinsic modules. Why is it necessary to have custom code for each new intrinsic module? Would it not be better, as I wrote elsewhere, to have .mod files and a library in a special directory for intrinsic modules? That way, the existing module code could be used, with the addition of your bits to sort out intrinsic and non-intrinsic.
What structure has Christopher adopted?
You'll have to find the module symbol, check if it's intrinsic and throw on the new module being non-intrinsic.b) the code USEing non-intrinsic modules (in module.c) to issue an error if an intrinsic module of the same name was already USEd; ie, I'd like the following to error out (while, with my patch, it does not):
...and the other way round, I suppose!module iso_fortran_env end module iso_fortran_env
program foo use, intrinsic :: iso_fortran_env use, non_intrinsic :: iso_fortran_env ! This should issue an error end program foo
convince me that what you are doing is OK!
Attachment:
iso_fortran_env.ChangeLog
Description: Binary data
Attachment:
iso_fortran_env.diff
Description: Binary data
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |