Re: problem with pointer and module
From: Jugoslav Dujic (jdujicREMOVE_at_uns.ns.ac.yu)
Date: 10/15/03
- Next message: Jugoslav Dujic: "Re: Pointers and allocatables"
- Previous message: Arjen Markus: "Re: Leaking Memory on Assignment(=) Interface"
- In reply to: Richard Maine: "Re: problem with pointer and module"
- Next in thread: john: "Re: problem with pointer and module"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 15 Oct 2003 09:23:11 +0200
Richard Maine wrote:
|
| Compilation of a module generally produces 2 files. One file usually
| has a .mod prefix and is used in subsequent compilation steps. You
| might loosely think of it as an automatically generated .h file and
| the USE statement as including it. This isn't exactly right, as the
| .mod file won't be in source code form like a .h file would be, but it
| still isn't a bad analogy.
Many C/C++ compilers support the feature of "precompiled headers"
(.pch in MSVC++ incarnation), which speeds up the compilation,
especially with large .h files. I think this is a pretty good
analogy.
-- Jugoslav ___________ www.geocities.com/jdujic
- Next message: Jugoslav Dujic: "Re: Pointers and allocatables"
- Previous message: Arjen Markus: "Re: Leaking Memory on Assignment(=) Interface"
- In reply to: Richard Maine: "Re: problem with pointer and module"
- Next in thread: john: "Re: problem with pointer and module"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|