| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 144.1 | | QUARK::LIONEL | Free advice is worth every cent | Wed Feb 05 1997 10:48 | 6 |
| You don't. The text library doesn't know you have "modules" - all it sees is
records of text from a file. In a text library, the module is the file.
If you want four different modules, then you have to insert them separately
with different names.
Steve
|
| 144.2 | | AUSS::GARSON | DECcharity Program Office | Wed Feb 05 1997 22:04 | 11 |
| re .0
I'm not familiar with that syntax "C$/MEMBER=xxx". Neither is the
librarian.
(I assume it's some new whizz bang feature of FORTRAN that allows
additional directives to the compiler. If so, only the FORTRAN compiler
understands it. Going further out on a limb, if it really controls the
object modules that the compiler produces then, by virtue of the
compiler having done its job, the librarian in processing the resulting
object file may well recognise the separate modules.)
|
| 144.3 | | QUARK::LIONEL | Free advice is worth every cent | Thu Feb 06 1997 11:30 | 4 |
| Fortran doesn't understand it either - at least not our Fortran. It looks
like a comment to us.
Steve
|
| 144.4 | | AUSS::GARSON | DECcharity Program Office | Thu Feb 06 1997 17:09 | 6 |
| re .3
I thought there was some kind of CDEC$ line beginning that, as you point
out, can be treated by the compiler as a comment but which can "encode"
certain additional directives but I have no recollection of what the valid
directives are. "Is this the real life or is this just fantasy?"
|
| 144.5 | as real as REAL*16 .. | COMEUP::SIMMONDS | lock (M); while (not *SOMETHING) { Wait(C,M); } unlock(M) | Thu Feb 06 1997 20:01 | 48 |
| Re: .4
$ help/noinstr/nopromp fortran state direc
FORTRAN
Statements
Directive_Statements
CDEC$ ALIAS name, external-name
CDEC$ ASSERT (e)
CDEC$ END OPTIONS (see CDEC$ OPTIONS)
CDEC$ IDENT string
CDEC$ INIT_DEP_FWD
CDEC$ NOVECTOR
CDEC$ OPTIONS /qual...
CDEC$ PSECT /common-name/ attr [,attr,...]
CDEC$ SUBTITLE string
CDEC$ TITLE string
CPAR$ CONTEXT_SHARED var_name[,...,var_name]
CPAR$ CONTEXT_SHARED_ALL
CPAR$ DO_PARALLEL [distribution-size]
CPAR$ LOCKON lock-variable
CPAR$ LOCKOFF lock-variable
CPAR$ PRIVATE name[,...,name]
CPAR$ PRIVATE_ALL
CPAR$ SHARED common_name[,...,common_name]
CPAR$ SHARED_ALL
You can use directives in a Fortran source program to influence
certain aspects of the compilation process.
Directives are prefixed, starting in column 1, with a 5-character
identifier and a space (or tab). Directives prefixed with CDEC$
are enabled in all Fortran compilation units, regardless of the
qualifiers used on the FORTRAN command line.
Directives may also be prefixed with a first character of ! (!DEC$
or !PAR$) in any column of a source line as long as only whitespace
(blanks or tabs) precedes the directive prefix.
Directives prefixed with CPAR$ are enabled only in Fortran
compilation units involved in parallel processing (that is, when
the /PARALLEL qualifier is specified on the FORTRAN command line).
If the /PARALLEL qualifier is not specified, parallel-processing
[...]
|
| 144.6 | | QUARK::LIONEL | Free advice is worth every cent | Fri Feb 07 1997 10:22 | 6 |
| Re: .4
As .5 indicates, there are indeed comment-like directives understood by
Digital Fortran. But they don't look like the comments in .0.
Steve
|