- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dear All:
As I have had an enjoyable struggle with SQL and Fortran, it took 4 weeks to get my level of understanding up to a point where I could do useful work. But now I have the ability to store data and retrieve it from SQL Server.
Almost all of the Fortran problems I had could be resolved with my
1. Powerstation Fortran Manual, it travels whereever I travel in my backpack - 2 book set.
2. Microsoft Fortran Manuals ditto.
I could not afford to use your HTML files, it takes to much time. I did find that this worked for me:
1. Take all the include modules such as:
[bash]! * ! ********************************************************************************** ! * * ! * INTEL CORPORATION * ! * Copyright (C) 2003-2011 Intel Corporation. All Rights Reserved. * ! * * ! * Portions Copyright 1992-2002, Hewlett-Packard Corporation. All Rights * ! * Reserved. * ! * Portions Copyright 1985-2001, Microsoft Corporation. All rights reserved. * ! * * ! * The source code contained or described herein and all documents related to * ! * the source code ("Material") are owned by Intel Corporation or its suppliers * ! * or licensors. Title to the Material remains with Intel Corporation or its * ! * suppliers and licensors. The Material contains trade secrets and proprietary * ! * and confidential information of Intel or its suppliers and licensors. The * ! * Material is protected by worldwide copyright and trade secret laws and * ! * treaty provisions. No part of the Material may be used, copied, reproduced, * ! * modified, published, uploaded, posted, transmitted, distributed, or * ! * disclosed in any way without Intel's prior express written permission. * ! * * ! * No license under any patent, copyright, trade secret or other intellectual * ! * property right is granted to or conferred upon you by disclosure or delivery * ! * of the Materials, either expressly, by implication, inducement, estoppel or * ! * otherwise. Any license under such intellectual property rights must be * ! * express and approved by Intel in writing. * ! * * ! ********************************************************************************** ! * !DEC$ IF .NOT. DEFINED (USER32_ ) !DEC$ DEFINE xUSER32_ ! ! ! ! *****USER32.LIB Interfaces***** ! ! This module defines routine interfaces to the Windows APIs ! for both the 32-bit (_M_IX86) and 64-bit (_M_IA64) versions of the ! NT4 and WIN2000 operating systems. ! ! The base for this version is: ! ! Microsoft Platform Software Development Kit (SDK) ! for Windows Server 2003 R2 ! ! As with the C header files distributed with the SDK, there ! is only one common set of files for both 64-bit and 32-bit ! operating systems. ! ! Within the Fortran versions of the header files, the ! following symbols are used to control the compilation. ! ! _M_IA64 conditionally compiles items for Intel IA-64 architecture systems ! _M_IX86 conditionally compiles items for Intel IA-32 architecture systems ! _M_X64 or __x86_64__ conditionally compiles items for the Intel 64 systems ! module user32 use ifwinty !DEC$OBJCOMMENT LIB:"USER32.LIB" ! INTERFACE FUNCTION wvsprintf( & arg1, & arg2, & arglist) use ifwinty integer(SINT) :: wvsprintf ! int !DEC$ ATTRIBUTES DEFAULT, STDCALL, DECORATE, ALIAS:'wvsprintfA' :: wvsprintf !DEC$ ATTRIBUTES REFERENCE, ALLOW_NULL :: arg1 character*(*) arg1 ! LPSTR arg1 !DEC$ ATTRIBUTES REFERENCE, ALLOW_NULL :: arg2 character*(*) arg2 ! LPCSTR arg2 TYPE(T_VA_LIST) arglist ! va_list arglist END FUNCTION END INTERFACE[/bash]
Load them into a WORD Document and the PDF the result. I could then search on key words.
Works a real treat.
The CHM file you had for the older compliers also worked quite well.
Really 90% of your manuals date from the 1980s and 1990's - republish those as PDF's.
JMN
As I have had an enjoyable struggle with SQL and Fortran, it took 4 weeks to get my level of understanding up to a point where I could do useful work. But now I have the ability to store data and retrieve it from SQL Server.
Almost all of the Fortran problems I had could be resolved with my
1. Powerstation Fortran Manual, it travels whereever I travel in my backpack - 2 book set.
2. Microsoft Fortran Manuals ditto.
I could not afford to use your HTML files, it takes to much time. I did find that this worked for me:
1. Take all the include modules such as:
[bash]! * ! ********************************************************************************** ! * * ! * INTEL CORPORATION * ! * Copyright (C) 2003-2011 Intel Corporation. All Rights Reserved. * ! * * ! * Portions Copyright 1992-2002, Hewlett-Packard Corporation. All Rights * ! * Reserved. * ! * Portions Copyright 1985-2001, Microsoft Corporation. All rights reserved. * ! * * ! * The source code contained or described herein and all documents related to * ! * the source code ("Material") are owned by Intel Corporation or its suppliers * ! * or licensors. Title to the Material remains with Intel Corporation or its * ! * suppliers and licensors. The Material contains trade secrets and proprietary * ! * and confidential information of Intel or its suppliers and licensors. The * ! * Material is protected by worldwide copyright and trade secret laws and * ! * treaty provisions. No part of the Material may be used, copied, reproduced, * ! * modified, published, uploaded, posted, transmitted, distributed, or * ! * disclosed in any way without Intel's prior express written permission. * ! * * ! * No license under any patent, copyright, trade secret or other intellectual * ! * property right is granted to or conferred upon you by disclosure or delivery * ! * of the Materials, either expressly, by implication, inducement, estoppel or * ! * otherwise. Any license under such intellectual property rights must be * ! * express and approved by Intel in writing. * ! * * ! ********************************************************************************** ! * !DEC$ IF .NOT. DEFINED (USER32_ ) !DEC$ DEFINE xUSER32_ ! ! ! ! *****USER32.LIB Interfaces***** ! ! This module defines routine interfaces to the Windows APIs ! for both the 32-bit (_M_IX86) and 64-bit (_M_IA64) versions of the ! NT4 and WIN2000 operating systems. ! ! The base for this version is: ! ! Microsoft Platform Software Development Kit (SDK) ! for Windows Server 2003 R2 ! ! As with the C header files distributed with the SDK, there ! is only one common set of files for both 64-bit and 32-bit ! operating systems. ! ! Within the Fortran versions of the header files, the ! following symbols are used to control the compilation. ! ! _M_IA64 conditionally compiles items for Intel IA-64 architecture systems ! _M_IX86 conditionally compiles items for Intel IA-32 architecture systems ! _M_X64 or __x86_64__ conditionally compiles items for the Intel 64 systems ! module user32 use ifwinty !DEC$OBJCOMMENT LIB:"USER32.LIB" ! INTERFACE FUNCTION wvsprintf( & arg1, & arg2, & arglist) use ifwinty integer(SINT) :: wvsprintf ! int !DEC$ ATTRIBUTES DEFAULT, STDCALL, DECORATE, ALIAS:'wvsprintfA' :: wvsprintf !DEC$ ATTRIBUTES REFERENCE, ALLOW_NULL :: arg1 character*(*) arg1 ! LPSTR arg1 !DEC$ ATTRIBUTES REFERENCE, ALLOW_NULL :: arg2 character*(*) arg2 ! LPCSTR arg2 TYPE(T_VA_LIST) arglist ! va_list arglist END FUNCTION END INTERFACE[/bash]
Load them into a WORD Document and the PDF the result. I could then search on key words.
Works a real treat.
The CHM file you had for the older compliers also worked quite well.
Really 90% of your manuals date from the 1980s and 1990's - republish those as PDF's.
JMN
Link Copied
2 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Why the need to convert to PDF? Isn't that just a complicated way of doing a "find in files" on the compiler's include directories?
Within VS2010 you can set up a folder group to point to "C:\Program Files\Intel\Composer XE\compiler\include" and then the search operation becomes almost trivial (perhaps it would be nice if the integration installation set this folder group for us, like VC++ does).
Within VS2010 you can set up a folder group to point to "C:\Program Files\Intel\Composer XE\compiler\include" and then the search operation becomes almost trivial (perhaps it would be nice if the integration installation set this folder group for us, like VC++ does).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the idea, excellent one.
JMN
JMN
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page