<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Modules - why? in Software Archive</title>
    <link>https://community.intel.com/t5/Software-Archive/Modules-why/m-p/969064#M23520</link>
    <description>Modules and .lib files are sort of apples and oranges.  It's easier to think of modules as an improvement on INCLUDE files.  A module allows you to have a self-consistent set of declarations, including constants, types, variables and routines, that is compiled separately.  A USE statement makes the public declarations from the module available to your routine, and if you call module routines, the interfaces are checked (something you wouldn't get with just a .LIB file)  You can restrict which names are visible from a module, select the names you want to import, and rename others.  Modules can USE other modules, so you have nested inheritance.&lt;BR /&gt;&lt;BR /&gt;There are many other advantages of modules - I suggest reading a good book on Fortran 90 to learn more.&lt;BR /&gt;&lt;BR /&gt;Oh, by the way, .LIB files are a great place to put the object files created when you compile a module.&lt;BR /&gt;&lt;BR /&gt;Steve</description>
    <pubDate>Thu, 11 Oct 2001 02:13:50 GMT</pubDate>
    <dc:creator>Steven_L_Intel1</dc:creator>
    <dc:date>2001-10-11T02:13:50Z</dc:date>
    <item>
      <title>Modules - why?</title>
      <link>https://community.intel.com/t5/Software-Archive/Modules-why/m-p/969063#M23519</link>
      <description>I've read the CVF documentation about Modules, including the advantages section. However, I'm still not sure about when to use them. Why use them over a .lib file for instance...? Am I missing something?</description>
      <pubDate>Thu, 11 Oct 2001 00:05:55 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Modules-why/m-p/969063#M23519</guid>
      <dc:creator>Intel_C_Intel</dc:creator>
      <dc:date>2001-10-11T00:05:55Z</dc:date>
    </item>
    <item>
      <title>Re: Modules - why?</title>
      <link>https://community.intel.com/t5/Software-Archive/Modules-why/m-p/969064#M23520</link>
      <description>Modules and .lib files are sort of apples and oranges.  It's easier to think of modules as an improvement on INCLUDE files.  A module allows you to have a self-consistent set of declarations, including constants, types, variables and routines, that is compiled separately.  A USE statement makes the public declarations from the module available to your routine, and if you call module routines, the interfaces are checked (something you wouldn't get with just a .LIB file)  You can restrict which names are visible from a module, select the names you want to import, and rename others.  Modules can USE other modules, so you have nested inheritance.&lt;BR /&gt;&lt;BR /&gt;There are many other advantages of modules - I suggest reading a good book on Fortran 90 to learn more.&lt;BR /&gt;&lt;BR /&gt;Oh, by the way, .LIB files are a great place to put the object files created when you compile a module.&lt;BR /&gt;&lt;BR /&gt;Steve</description>
      <pubDate>Thu, 11 Oct 2001 02:13:50 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Modules-why/m-p/969064#M23520</guid>
      <dc:creator>Steven_L_Intel1</dc:creator>
      <dc:date>2001-10-11T02:13:50Z</dc:date>
    </item>
  </channel>
</rss>

