Professional Documents
Culture Documents
Software Version:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
________________________________________________________________
2001 Compaq Computer Corporation
COMPAQ and the Compaq Logo are registered in the U.S.
Patent and Trademark Office.
AlphaGeneration, AlphaServer, DEC Fortran, OpenVMS,
and Tru64 UNIX are trademarks of Compaq Information
Technologies, L.P.
Microsoft, NT, Visual Basic, Visual C++, and Windows are
either trademarks or registered trademarks of Microsoft
Corporation in the United States and other countries.
Intel and Pentium are trademarks of Intel Corporation.
AMD and Athlon are trademarks of Advanced Micro Devices,
Inc.
Adobe and Acrobat are trademarks of Adobe Systems
Incorporated.
GLOBEtrotter and FlexLM are trademarks of GLOBEtrotter
Software, Inc.
ISML and Visual Numerics are trademarks of Visual Numerics,
Inc.
All other product names mentioned herein may be trademarks
of their respective companies.
Confidential computer software. Valid license from Compaq
required for possession, use or copying. Consistent with
FAR 12.211 and 12.212, Commercial Computer Software,
Computer Software Documentation, and Technical Data for
Commercial Items are licensed to the U.S. Government under
vendor's standard commercial license.
Compaq shall not be liable for technical or editorial
errors or omissions contained herein. The information
in this document is provided "as is" without warranty
of any kind and is subject to change without notice. The
warranties for Compaq products are set forth in the express
limited warranty statements accompanying such products.
Nothing herein should be construed as constituting an
additional warranty.
Major changes since Version 6.5A are indicated in blue
color in HTML output and by change bars in the margin in
the plain ASCII TXT output.
This document was prepared using DECdocument, Version 3.31n.
_________________________________________________________________
Contents
1 Introduction
1.1
1.2
1.3
Conventions...................................
Overview......................................
General Information...........................
1-2
1-2
1-2
2 Installation Notes
2.1
2.2
2.3
2-1
2-3
2-4
3 Version 6 News
3.1
3.2
3.3
3.3.1
3.3.2
3.3.3
3.4
3-1
3-3
3-4
3-5
3-10
3-15
3-20
4-1
4-6
4-11
4-17
4-21
iii
5-1
5-6
5-7
5-9
5-14
5-18
6-1
6-2
6-6
6-7
6-9
6-9
7-1
7-2
7-2
7-4
iv
8-1
8-1
8-2
8-2
9-2
9-2
1
_________________________________________________________________
Introduction
Thank you for choosing Compaq Visual Fortran. This document
provides release notes for Compaq Visual Fortran Version
6.6. It also provides key information for earlier releases
since Version 6.0.
Compaq Visual Fortran conforms to the Fortran 95 Standard,
Fortran 90 Standard, and previous Fortran standards.
Compaq Visual Fortran uses the same robust compiler system
provided with Compaq Fortran on other platforms for Alpha
systems.
Please visit the Compaq Fortran Web page for a wealth of
information about Compaq Visual Fortran and Compaq Fortran,
including product descriptions, product updates, frequently
asked questions, knowledge base articles, example programs,
and other information: http://www.compaq.com/fortran
It is important that you register your purchase of
Compaq Visual Fortran (Visual Fortran) and also keep your
registration information (such as your e-mail address) upto-date. Registration entitles you to exclusive benefits,
such as the Visual Fortran Newsletter, and provides a
record of your serial number should you misplace it.
Concurrent license users need to perform a separate
registration to obtain the license key, but concurrent
license users (like other users) should also register their
Visual Fortran purchase. Use the following Internet URL:
http://www.compaq.com/fortran/register
Introduction 1-1
1.1 Conventions
In these release notes:
o Compaq Visual Fortran is often abbreviated as "VF" or
"CVF".
o Compaq Array Visualizer is often abbreviated as "AV" or
"CAV".
1.2 Overview
These release notes describe Compaq Visual Fortran Version
6.6 and previous releases back to Version 6.0:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
will be installed
required. VF online
Internet Explorer V4,
Fortran installation
|
|
|
1-4 Introduction
2
_________________________________________________________________
Installation Notes
This chapter presents important points to consider and
actions to take to ensure a successful installation of
Compaq Visual Fortran:
o Section 2.1, Version 6.6 Installation Notes
o Section 2.2, Installation Changes for Version 6.5 to
Typical Installation
o Section 2.3, Installation Notes Related to Online
Documentation
2.1 Version 6.6 Installation Notes
The v6.6 installation procedure is the same as for v6.5.
Please refer to the Compaq Fortran Installing and Getting
Started guide for installation instructions (see the
printed book or online file Cvf_gs.pdf).
The following installation notes apply to the current
version of Visual Fortran:
o If you attempt to install Visual Fortran v6.* using
any of the methods described in "Installing and Getting
Started - Using Setup to Install Visual Fortran", and
SETUP.EXE in the root directory fails to run, on x86
systems, run: \X86\SETUPX86.EXE
This runs the same installation procedure as SETUP.EXE
in the root directory.
o Visual Fortran v6.* and Microsoft Visual C++ v6.0 are
engineered to co-exist in Microsoft Developer Studio.
However, the versions of all products MUST match or
you will receive version mismatch errors when starting
Developer Studio. An example of the error message you
would receive is:
Installation Notes 2-1
|
|
|
|
After you install Visual Fortran, you can run the HTML
Help Viewer to view the online documentation. If you
install Visual Fortran using the "Run From CD-ROM"
option, the first time you access the index (such as
clicking the index tab, pressing F1, or if you start
HTML Help Viewer by clicking Index in the Help menu),
a "building index for first use" message box appears.
There will be a delay of 10-20 minutes while HTML Help
Viewer creates a df60.chw index file in the folder
...\Microsoft Visual Studio\df98\doc. The df60.chw file
is approximately 20 MB.
In addition to disk space requirements for installing
Visual Fortran in "Run From CD-ROM" mode, the disk where
Visual Fortran is installed must have enough room after
installation for building the df60.chw file, if you
intend to use the documentation index.
There also needs to be at least 30MB free on the disk
where the windows temp directory resides while the
df60.chw file is being built.
o If you also install the MSDN (or Visual Studio)
documentation
If you also install the MSDN documentation from CD-ROM,
be aware that you must switch between displaying the
MSDN documentation collection and the Visual Fortran
documentation collection in HTML Help Viewer. With
Windows 2000 systems, be aware that your account needs
at least Power User privilege to change collections. To
change the collection of titles displayed in HTML Help:
1. Start the visual development environment (Start->
Compaq Visual Fortran->Developer Studio)
2. In the Tools menu, click Options.
3. Scroll to the Help System tab
4. In the Preferred Collection box, select either the
Visual Fortran or the MSDN Library as your current
collection.
5. Click OK. The collection you just selected is now
your current collection.
Installation Notes 2-5
3
_________________________________________________________________
Version 6 News
This chapter describes Version 6.6 news, notes, and known
problems. It also provides news for previous releases and
supplemental notes.
o Section 3.1, Version 6.6 News
o Section 3.2, Version 6.6 Known Problems
o Section 3.3, Version 6 News
o Section 3.4, Version 6 Notes and Supplemental
Information
3.1 Version 6.6 News
The following are new and changed features for v6.6:
o
o
o
o
|
|
INTEGER (KIND=8) and LOGICAL (KIND=8) are now recognized |
to support 64-bit signed integers.
|
|
When the /fast command line option is present, if any
|
of the forms of /stand are present, /fast will not set
|
/align=dcommons and /align=sequence.
|
|
The command line option /stand now defaults to F95 not
|
F90.
|
|
New compiler option keyword /fpscomp:[no]ldio_spacing
|
|
The Fortran 95 Standard requires that there be a blank
|
after a numeric value before a character value in list- |
directed output. Microsoft PowerStation did not do
|
this; nor did VF v6.5A. As of v6.6, VF will obey the
|
F95 Standard by default {/FPSCOMP:NOLDIO_SPACING}. If
|
/FPSCOMP:LDIO_SPACING is specified, VF will produce
|
the old, non-standard output. /FPSCOMP:GENERAL will set |
/FPSCOMP:LDIO_SPACING.
|
Version 6 News 3-1
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
VF still accepts the old spellings of the keywords for
|
"xxx".
|
|
o A derived-type variable which is data initialized via
|
default initialization of any of its components will no |
longer be saved by default. A RECORD variable which is
|
data initialized via default initialization specified
|
in its STRUCTURE declaration will no longer be saved by |
default.
|
|
o fpp supports the macros __DATE__ and __FILE__. When
|
fpp is told to expand macros using "-fpp:-m", these
|
expand into character literals that give the name of the |
source file being processed and the current date/time
|
respectively.
|
|
character*20 file
|
character*20 date
|
file = __FILE__
|
date = __DATE__
|
type *, file, date
|
end
|
|
Do not put __DATE__ or __FILE__ inside quotes in the
|
source.
|
|
3.2 Version 6.6 Known Problems
The following known problems remain in VF:
|
|
o Control C handlers
|
|
Problems have been reported with implementing console
|
event handlers (e.g., control C handlers) in programs
|
built with Visual Fortran. The symptom is usually that
|
the handler is seemingly never invoked. This is due
|
to the implementation of console event handling on
|
WIN32 platforms. In response to a Control-C event, the
|
operating system will create a new thread to execute the |
handler in. In order for the new thread to execute, it
|
must obtain priority. If the currently executing thread |
does not relinquish its priority, it is possible that
|
program execution will terminate before the console
|
event handler ever executes. For example, a READ
|
statement directed at the console which is interrupted
|
Version 6 News 3-3
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Version 6.5A news:
|
|
o The "unused" variable message is informational, not a
|
warning, as of 6.5A.
|
|
o The Fortran COM Server Wizard now allows you to select
|
an out-of-process (.EXE) COM server. Users now have a
|
choice of the type of server: either a DLL (in-process) |
COM server or an EXE (out-of-process) COM server.
|
|
o New compiler options and their descriptions:
|
|
- /assume:[no]protect_constants
|
|
This option specifies whether constant actual
|
arguments can be changed. By default, actual
|
arguments that are constants are read-only
|
(/assume:protect_constants). To allow changes
|
to actual arguments that are constants, specify
|
/assume:noprotect_constants.
|
|
- /check:[no]arg_temp_created
|
|
Requests that a run-time informational message appear |
if actual arguments are copied into temporary storage |
before routine calls. Specifying /check:noarg_temp_
|
created (the default) does not generate the extra
|
code needed to display a message run-time when this
|
condition occurs.
|
|
- /warn:[no]ignore_loc
|
|
Requests that the compiler issues warnings when
|
%LOC is stripped from an argument. The default is
|
/warn:noignore_loc (does not issue a warning for this |
condition).
|
|
o The hardware selected by the /ARCH command line option
|
is the basis for the /TUNE option, i.e., you cannot use |
/TUNE to tune generated code for an architecture older
|
than the one selected by /ARCH.
|
|
o New data ATTRIBUTES directive keywords are now
|
available:
|
|
ALLOW_NULL, DECORATE, IGNORE_LOC, and NOMIXED_STR_LEN_
|
ARG
|
Version 6 News 3-5
|
|
|
|
|
|
|
|
|
|
|
|
|
|
nd
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
-D_MT=1
If compiling threaded
If Windows 95
-D_WIN98=1
If Windows 98
-D_ALPHA_=1 (both
compiler and FPP)
If Alpha
-D_MSFORTRAN_=401
If /fpscomp:all or
/fpscomp:symbols
-D_DLL=1
/D__LANGUAGE_FORTRAN______To_FPP_only___________________
The user may define additional symbols, such as -D_
BUILDING_DLL=1 to mean that the compilation is building
a DLL.
o A new item has been added to the Developer Studio File
menu, "Print Colorized Fortran...". This item prints a
Fortran source file in color. It uses the FSC utility,
described elsewhere in the release notes, to create
an HTML file with the coloring information. It then
instructs the application on your system that handles
w/len
no len
reference__no_len___no_len___no_len____no_len______no_len________
This was how Microsoft PowerStation originally specified
this behavior, so VF specified it too. However, there
was no ability to pass a character argument with the
hidden length *and* using the STDCALL attribute for the
function. This was a major problem that did not occur
with the C attribute because specifying C+REFERENCE did
pass the length. Also, this was the only case where the
C+REFERENCE behavior varied from the STDCALL+REFERENCE
behavior.
As a result, the STDCALL+REFERENCE behavior has been
modified (when no attribute is given to the argument)
to match the C+REFERENCE behavior, i.e. pass both the
address and the hidden length in this case. This allows
the use of STDCALL while still being able to pass the
address of character arguments with or without the
hidden length.
3-18 Version 6 News
\Misc\WHAT.EXE
\Misc\STRSUB.EXE
_________________________________________________________________
...\Support
Directory___________Description__________________________________
\Misc\FIXMSTAB.EXE This program converts Fortran source code
that uses Microsoft style tab rules to follow
Compaq Fortran standard TAB rules.
\Misc\CBANLC.EXE
\Misc\CBANLW.EXE
4
_________________________________________________________________
Visual Fortran Compiler Release Notes
This chapter provides the following details about changes
to the Compaq Fortran compiler:
o Section 4.1, New Features and Changes for Version 6.6
o Section 4.2, New Features and Changes for Version 6.5A
o Section 4.3, New Features and Changes for Version 6.5
o Section 4.4, New Features and Changes for Version 6.1A
o Section 4.5, Features of Microsoft Fortran PowerStation
Not Supported
4.1 New Features and Changes for Version 6.6
|
|
The following changes have been made to the Compaq Fortran |
compiler for VF v6.6 since VF v6.5A shipped:
|
|
o The following changes have been made to the compiler
|
{from V6.6-1657-47B5I to V6.6-1684-47B6E}:
|
|
- Do NOT evaluate the argument to any numeric inquiry
|
function (like HUGE). The evaluation may kill the
|
stack (for a large array argument, even without a
|
function call). CVF14579.
|
|
- Make actual argument which is a function returning a |
scalar pointer work correctly. CVF14525.
|
|
- BOZ constants are allowed for integer initialization. |
|
- Fix access to module from path specified on command
|
line.
|
|
- Array passing optimization was not working correctly |
for assumed-shape arrays being passed as explicit
|
arrays.
|
Visual Fortran Compiler Release Notes 4-1
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- Handle use of a contained function in bounds
|
expression of following procedure.
|
|
- Fix bug in the NT driver where it would accvio if
|
a MS-style qualifier that required a value was put
|
at the end of a line, and did not have its required
|
value.
|
|
- Update intrinsic functions COUNT and ZEXT to allow
|
optional 'KIND' argument.
|
|
- Get the debug locator correct for all ENTRY SYMBOLs. |
|
- Inhibit release of warning: 'Symbol in block data
|
program unit is not in a COMMON block' if the symbol |
has a 'use'. To allow use in implied do of data
|
initialization. If other use , earlier diagnostic
|
would have been issued.
|
|
- For CVF 6.6 and later, always look for a FLEXlm
|
license.
|
|
o The following changes have been made to the compiler
|
{from T6.6-1495-47B38 to T6.6-1567-47B4D}:
|
|
- Make sure that type associated with function result
|
gets added to list for export.
|
|
- Fix problem with importing generic symbol.
|
|
- Fix problem with importing common symbol which is
|
renamed.
|
|
- Implement correct ALIGN=xx values; support ALIGN=PAGE |
on all platforms (which is new) and set the alignment |
to whatever a "page" means on that platform.
|
|
- Generate better debug information for dummy arguments |
which are subroutines or functions.
|
|
- Do the right thing on Intel if number_of_processors
|
is being stored to an integer*8.
|
|
- If /integer_size:64 is set, the conditional
|
compilation code would generate errors saying
|
"invalid conditional compilation expression".
|
Visual Fortran Compiler Release Notes 4-3
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- Mark the array descriptor for an explicitly shaped
|
array function result as quadword aligned.
|
|
o The following changes have been made to the compiler
|
{from V6.5-1332-44ACE to T6.6-1495-47B38}:
|
|
- Make /STANDARD (-stand) mean F95, not F90.
|
|
- When merging specific procedure lists from different |
modules, allow multiple definitions for generics.
|
|
- Recognize /fpscomp:libs in compiler for *_WNT
|
environments.
|
|
- Diagnose missing intent attributes on pure
|
(explicitly or implicitly if elemental) subroutine
|
arguments which are neither pointers nor procedures. |
|
- Support INTEGER(KIND=8) and LOGICAL(KIND=8) as 64-bit |
signed integers.
|
|
- Diagnose mask expressions with incompatible shapes in |
where constructs and contained where/elsewheres.
|
|
- Impose standard restriction that defined-operator
|
names consist only of letters.
|
|
- Allow /fpscomp:[no]ldio_spacing.
|
|
- When /fpscomp:general is specified. set
|
/fpscomp:ldio_spacing. (CVF13066)
|
|
- /warn:trucated_source must be set even if /stand:f95 |
is to get "truncated source" message.
|
|
- Do not loose place in source stream when see zero|
padded-integer.
|
|
- Repair another field-dot problem in defined
|
operators.
|
|
- For COMPLEX*16 results, special case CCOS, CEXP,
|
CLOG, CSIN, CSQRT to be type of arg; similarly for
|
REAL*8 and ALOG, ALOG10.
|
Visual Fortran Compiler Release Notes 4-5
|
|
|
|
|
|
|
|
|
|
5
_________________________________________________________________
Visual Fortran RTL Release Notes
This chapter provides the details about the following
changes to the Compaq Fortran run-time library (RTL)
system:
o Section 5.1, New Features and Changes for Version 6.6
o Section 5.2, Restrictions and Known Problems
o Section 5.3, New Features and Changes for Version 6.5A
o Section 5.4, New Features and Changes for Version 6.5
o Section 5.5, New Features and Changes for Version 6.1A
o Section 5.6, Run-Time Differences Between Visual Fortran
and Microsoft Fortran PowerStation
5.1 New Features and Changes for Version 6.6
The following changes have been made to the Compaq Fortran
run-time library (RTL) system for VF v6.6 since VF v6.5A
shipped:
o The following v6.6 changes have been made to the RTL
{-867}:
- Modifications were made to advapi32.{f90|mod} to
correct some problems that were identified.
- Modification to dfwinty.{f90|mod} to change the
definition of wchar from 1 to 2. This change
potentially propagates through all the other header
files, including those used in dfcom, dfauto,
dialogm.
- Comctl32 related changes/fixes done to
dfwinty.{f90|mod}
Visual Fortran RTL Release Notes 5-1
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Under /fpe:0, the Fortran rtl default exception
|
handler would sometimes cause an access violation
|
while attempting to flush an underflow result to
|
zero. (cvf13016)
|
|
The Fortran RTL was not properly processing the input |
for a sequential or internal list directed read when |
the data contained a complex value with a repeat
|
count before it. Additionally, the number of digits
|
in the real part of the complex had to be less than
|
the number of digits in the imaginary part, i.e.,
|
10*(-1,1). This problem has been fixed. (cvf13179)
|
|
An error with list directed input dealing with an
|
asterisk, "*", that ended a non-delimited character
|
string that was immediately followed by a terminating |
comma was fixed. (cvf13556)
|
|
There are new versions of the module header files
|
DFWINTY.F90 and DFWIN.F90 (and its component files). |
These new module headers are designed to work in
|
both the 32-bit and 64-bit environments. Besides some |
additional content, the new data type definitions
|
and procedure interfaces to the Microsoft WIN32 APIs |
have been parameterized based on pointer size, and
|
coded in a way that makes it easy to see what the C
|
definition is.
|
|
For example: integer(LPVOID) Sacl ! pointers PACL
|
|
shows that Sacl is a pointer in two ways. LPVOID in
|
C indicates a pointer to any object, and the Fortran |
comment indicates that PACL was identified from a
|
list of known pointers. Most of the common C data
|
types have their own Fortran equivalent, and in most |
cases there is a comment showing the C definition.
|
|
These new header files require the following changes |
to the current set of sample programs:
|
|
...\SAMPLES\ADVANCED\WIN32\CHECK_SD\CHEK_SSD.F90
|
...\SAMPLES\ADVANCED\WIN32\TAKEOWN\TAKEOWN1.F90
|
|
Visual Fortran RTL Release Notes 5-3
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
For example:
|
|
bret = SetSecurityDescriptorOwner (
&
|
LOC(SecurityDescriptor)
&
|
AliasAdminsSid,
&
|
.FALSE.
&
|
)
|
|
The code for these interfaces is in ADVAPI32.F90
|
which is in the CVF INCLUDE library.
|
|
Please let us know if you have to make any changes
|
to your native Windows applications to make them work |
with the new module header files, or if you find any |
errors in the new definitions.
|
|
o The following v6.6 changes have been made to QuickWin:
|
|
- Palette(0) was incorrectly being used as the
|
background color when filling objects such as
|
rectangles and ellipses. This has been corrected.
|
The color set by SETBKCOLOR or SETBKCOLORRGB is now
|
used as the background when filling an object. This
|
background color is used when a bitmap (as set by
|
SETFILLMASK) controls the filling. (cvf11466)
|
|
- The graphics routines POLYBEZIER, POLYBEZIER_W,
|
POLYBEZIERTO, and POLYBEZIERTO_W have been added
|
to QuickWin. For specific information, please refer
|
to the on-line documentation. An example program may |
be found following the entry for POLYBEZIERTO and
|
POLYBEZIERTO_W. (cvf12920)
|
|
- It is now possible to configure a QuickWin window
|
so that it will always show the last line written
|
and the text cursor (if it is on) by scrolling the
|
screen. This is done by calling SETWINDOWNCONFIG.
|
|
To enable this feature, do the following (where
|
wc is of the derived type windowconfig): wc%mode =
|
QWIN$SCROLLDOWN
|
|
You should also fill in the other fields as suggested |
in the online documentation for SETWINDOWCONFIG.
|
(cvf11495, cvf13153)
|
|
Visual Fortran RTL Release Notes 5-5
= AAABBBCCCDDD
< >
< >
<
Font Families:
QWIN$EXTENDFONT_FF_ROMAN
QWIN$EXTENDFONT_FF_SWISS
QWIN$EXTENDFONT_FF_MODERN
QWIN$EXTENDFONT_FF_SCRIPT
Cursive, etc.
QWIN$EXTENDFONT_FF_DECORATIVE
Character Sets:
QWIN$EXTENDFONT_ANSI_CHARSET
QuickWin default.
QWIN$EXTENDFONT_OEM_CHARSET
PASS_DIR_TRUE
PASS_DIR_INSDEL
PASS_DIR_CNTRLC
6
_________________________________________________________________
Developer Studio Release Notes
This section contains the following information:
o Section 6.1, New Features and Changes for Version 6.6
o Section 6.2, Known Problems, Troubleshooting, and
Limitations
o Section 6.3, New Features and Changes for Version 6.5A
o Section 6.4, New Features and Changes for Version 6.5
o Section 6.5, New Features and Changes for Version 6.1A
o Section 6.6, New Features and Changes for Version 6.1
and 6.0
6.1 New Features and Changes for Version 6.6
|
|
The following changes have been made to Developer Studio
|
6.6 since VF v6.5A shipped:
|
|
o Developer Studio enhancements:
|
|
- Extended Project menu, Project Settings item, Fortran |
tab as follows:
|
|
* In the Fortran Data category, added support for
|
"Default Integer Kind" of 2, 4, or 8
|
|
* In the Library category page, the Use run-time
|
libraries list more closely resembles the same
|
category in the C/C++ tab and includes debug
|
versions.
|
|
* In the Listing category, added support for the
|
Annotations list box and /annotations keywords.
|
|
* In the Compatibility category under Microsoft
|
Fortran PowerStation, added support for List
|
Directed I/O Spacing (/fpscomp:ldio_spacing).
|
Developer Studio Release Notes 6-1
|
|
|
|
|
|
|
|
|
|
________________________________________________________
If_your_system_is:____Copy_the_file_to_this_directory:__
Windows 9*
Windows directory\system
Windows NT 4
Windows directory\system32
Windows_2000__________Do_not_copy_the_file______________
o When you select "Build browse info file" in the Browse
Info option page, Developer Studio may display the
following message:
"The Browser Information file will not be created unless
'Generate browse info' is checked on the C/C++ settings pa
ge for
the target or at least one file"
For Fortran-only Developer Studio projects, check
'Generate Source Browse Information' on the Fortran
page, General category. You do not need to set any C/C++
settings.
o When using the Source Browser in Developer Studio for
browsing Fortran code, be sure to uncheck the "Case
Sensitive" check box at the bottom of the "Browse"
dialog box. This allows the Source Browser to find
occurrences of Fortran symbols regardless of the case
used in the sources.
o If you receive "Unexpected error returned by Array
Visualizer" when attempting to view an array from the
debugger, please try the following. From a command
window, run:
REGSVR32 Windows directory\System32\ATL.DLL
o If the files created during a build appear to be out of
date, and you are running Visual Fortran on Windows 95
or Windows 98 operating systems, there is a possibility
that the timestamps on the files created during a build
can be off by up to 2 seconds. With faster machines
and performance improvements in the linker, this can
cause the .OBJ files to have a later timestamp than the
result of the linker. This makes some projects appear
out-of-date after a build and thus Visual Fortran may
incorrectly indicate that another link is needed. If
you encounter this problem, you can work around it by
adding a pre-link build rule to your project that takes
6-4 Developer Studio Release Notes
7
_________________________________________________________________
Visual Fortran Documentation Release Notes for Version 6
This section describes documentation changes for Visual Fortran:
o Section 7.1, Version 6.6 Documentation Changes
o Section 7.2, Version 6.5 and 6.5A Documentation Changes
o Section 7.3, Version 6.1 Documentation Changes
o Section 7.4, PDF Files, HTML Files, and Samples
7.1 Version 6.6 Documentation Changes
|
|
The online documentation has been updated for Version 6.6. |
|
New features as well as links to the new sections in the
|
online documentation are provided in New Features for
|
Compaq Visual Fortran Version 6.6, which is available in
|
HTML Help (online documentation) from the Visual Fortran
|
Home Page.
|
|
Information about support for Windows NT Alpha systems has |
been removed and some preliminary information about IA-64
|
support has been added. The following platform labels have |
been added to identify platform differences in text and
|
headings:
|
|
o IA-32 or ia32 only
|
|
o IA-64 or ia64 only
|
|
HTML versions of the revised Visual Fortran 6.6 and Array
|
Visualizer 1.6 online HTML Help documentation, the Compaq
|
Fortran Language Reference Manual, and the Compaq Visual
|
Fortran Installing and Getting Started are now provided
|
on the Visual Fortran CD-ROM (see Section 7.4). To view
|
these files, open the appropriate local disk files in a Web |
browser.
|
|
|
|
|
titles are
the folder
(open the file
Readme.txt from
- Language Reference
- Programmer's Guide
- Error Messages
- Array Visualizer
o A revised HTML version of the Compaq Visual Fortran
Installing and Getting Started is provided on the
Visual Fortran CD-ROM in the folder Info\Df\Doc\CVF_
HTML (open the file Readme.htm in a browser or view the
file Readme.txt from Info\Df\Doc\CVF_Html).
o Visual Fortran, CXML, and IMSL documentation are
provided as PDF files.
The Compaq Visual Fortran Installing and Getting Started
is available in Acrobat PDF format. Open the file Cvf_
gs.pdf on the Visual Fortran CD-ROM root directory in
Adobe Acrobat Reader. This file is also installed by
7-4 Visual Fortran Documentation Release Notes for Version 6
info\Df\Samples
info\Df\Samples\Samples.htm
x86\Samples
8
_________________________________________________________________
Debugging Related Release Notes
This chapter provides the details about the following
changes to the Compaq Fortran debugger support:
o Section 8.1, Changes Made to Version 6.6
o Section 8.2, Restrictions and Known Problems
o Section 8.3, New Features and Changes Made to Version
6.5 and 6.5A
o Section 8.4, New Features and Changes Made to Version
6.1A
8.1 Changes Made to Version 6.6
The following changes have been made to the debug support
for 6.6 since V6.5A shipped:
o Support was added to allow displaying and debugging of
INTEGER*8 variables.
o In previous versions, attempting to display an array
module variable in the array visualizer from the
debugger resulted in an error message. This has been
fixed.
8.2 Restrictions and Known Problems
Known problems with the current debug support:
o The return value for complex-valued functions does not
display properly if the function has alternate entry
points.
|
|
|
|
|
|
|
|
|
|
|
|
|
subroutine foo(i1,i2)
integer i1(:), i2(:)
integer problem(size(i1),size(i2))
.
.
contains
subroutine bar()
.
i3 = problem+1
! break set here, request 'problem' in
! watch window
.
.
.
previously caused Developer Studio to crash. This crash
no longer occurs. Note that the following restriction
does currently exist: such a variable ('problem' in the
above example) cannot be viewed from within an internal
subroutine (e.g. 'bar' above).
o The debugger would previously not display host
associated variables that were also dummy arguments
in the containing routine. This has been fixed.
o In previous versions of the product, format specifiers
had no effect on character variables in watch windows.
For example, trying to see a character variable 'ch'
in octal by typing "ch,o" in a watch window, had no
effect. Support has been added in this release for using
'o', and 'd'/'i' format specifiers to watch character
variables.
o There was a bug in previous versions that made it
impossible to watch an array section where the array
is a member of a derived type, such as:
type str
integer, pointer :: f(:,:)
end type str
type (str), pointer :: a(:)
allocate (a(3))
allocate (a(1)%f(10,1))
a(1)%f(:,1) = (/1,2,3,4,5,6,7,8,9,10/)
write(*,*)a(1)%f ! Previously not possible to watch
! a(1)%f(:,:)
Debugging Related Release Notes 8-3
9
_________________________________________________________________
Compaq Extended Math Library (CXML) Release Notes
Please read this section before installing or using the
Compaq Extended Math Library (CXML).
Visual Fortran Version 6.6 includes a new version of the
Compaq Extended Math Library (CXML), CXML Version 5.0 (see
Section 9.2).
|
|
|
Introductory
material and
features
Usage
Routine reference
Latest CXML
The CXML website at:
release
http://www.compaq.com/math
information________________________________________________
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Sample files which show how to invoke the direct sparse |
solver routines from Fortran 95/90, and C are available |
in the CXML Samples folder:
|
|
\Df98\CXML\Samples
|
|
The interface to the following sparse iterative solvers |
functions has been changed:
|
|
DMATVEC_SDIA
DMATVEC_GENR
|
DAPPLY_POLY_SDIA DAPPLY_POLY_GENR
|
|
The mechanism for printing messages in the iterative
|
solvers has been changed. Users now have an option to
|
either supply their own print routine (which is invoked |
by the iterative solvers to print messages) or have the |
messages printed out to the standard output device.
|
A detailed description of the new functionality is
|
provided in the "Using Iterative Solvers" section of
|
the CXML Reference Guide.
|
|
In the iterative solvers, the argument iounit no longer |
determines the kind of information to be printed. Now
|
the argument iolevel determines the level of information |
to be printed. In case of a negative value for iolevel, |
no information is printed. Refer to the CXML Reference
|
Guide for more details - examples are also provided that |
reflect the modifications required in the user's code
|
for the correct use of iterative solvers.
|
|
The auxiliary LAPACK routine XLAENV is no longer
|
supplied, or used, by CXML. The LAPACK routines DLAMCH
|
and SLAMCH have been modified to return compile time
|
constants instead of computing values on each call.
|
|
10
_________________________________________________________________
Compaq Array Visualizer Release Notes
This section provides release notes for Compaq Array
Visualizer:
o Section 10.1, New Features and Changes for Version 1.6
o Section 10.2, Array Visualizer Known Problems and
Limitations
o Section 10.3, New Features and Changes for Versions 1.5A
and 1.5
o Section 10.4, New Features and Changes for Versions
1.1A, 1.1, and 1.0
o Section 10.5, Compaq Array Visualizer Overview and
Description of Features
o Section 10.6, Using the Fortran Array Visualizer from
the Debugger
o Section 10.7, The Fortran Array Visualizer Uses HDF
Libraries
10.1 New Features and Changes for Version 1.6
The following changes have been made to the Compaq Array
Visualizer for v1.6 since VF v1.5A shipped:
o A problem in the Array Viewer has been fixed where a
program exception might occur when viewing an HDF file
if a dimension scale of a dataset has the same name as
the dataset.
o 8-byte integer types are now supported.
o A workaround for a Microsoft OpenGL bug that effects
Windows 2000 systems (cf: MS KB Q272222) has been
implemented.
Compaq Array Visualizer Release Notes 10-1
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
11
_________________________________________________________________
Fortran Format Editor Release Notes
There are no changes to the Format Editor for Version 6.6.
The following are limitations and supplemental notes about
the Fortran Editor:
o The Format Editor does not support "Variable Format
Expressions".
o The Format Editor does not support "Repeat
Specifications" greater than 99.
o Repeatable edit descriptors can be specified without
a field width value. Since the Format Editor does not
know the attributes of the Fortran data that will be
associated with the edit descriptor at run-time, it uses
a default field width based upon the type of the edit
descriptor. The following table lists the repeatable
edit descriptors and the default field width used by the
Format Editor for displaying the sample field data.
________________________________________________________
Edit
Descriptor______Default_Width___________________________
A
10
15
15
15
________________________________________________________
Edit
Descriptor______Default_Width___________________________
G
15
EN
15
ES______________15______________________________________