Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
29281 Discussions

Error in function CHANGEDRIVEQQ

karen4kids
Beginner
‎09-14-2009 02:48 PM
386 Views
I have recently converted from Visual Studio 6 with Compaq Visual Fortran to Visual Studio 2005 with Intel Fortran Compiler Integration for Microsoft Visual Studio 2005, 10.1.4156.2005. My complaint is with the IFPORT function CHANGEDRIVEQQ. The help file states:
CHANGEDRIVEQQ changes only the current drive. The current directory on the specified drive becomes the new current directory. If no current directory has been established on that drive, the root directory of the specified drive becomes the new current directory.
This is not true, although it was exactly correct in the Compaq Visual Fortran. Any time the function is called, the root directory of the specified drive becomes the curent directory, regardless of whether a current directory has been established.

If you are aware of any fixes to this problem, please let me know.
0 Kudos

Link Copied

1 Reply
Paul_Curtis
Valued Contributor I
‎09-14-2009 05:39 PM
386 Views

"Current drive" and "Current directory" are fictions which died with MS-DOS. Suggest you eliminate this entire problem by explicitly coding the complete path as a prefix to your filenames, then you always know exactly where each file is located.
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.