Microsoft Windows* 8.x

Submodule+coarray bug with IVF 16.0

The following code triggers compiler error #8361 (A coarray or an object with a coarray ultimate component shall be a dummy argument or have the ALLOCATABLE or SAVE attribute.) for coarray J. I think this is incorrect, but I may be wrong.

Using SAVE for J eliminates this error message.

MODULE A
INTEGER :: I[*]
END MODULE A

SUBMODULE (A) B
INTEGER :: J[*]
END SUBMODULE B

PROGRAM MAIN
USE A
END PROGRAM MAIN

 

Need an advice on programming graphic using either Visual Fortran or Visual C/C+

Dear All,

I have a project on fluid flow with graphics on. I am looking forward to continue developing the solver part in Fortran but the UI with a graphic console in mixed language form. I just need an advice that which one of the following two options is better;

passing a character string in c++ t oa dll function in Fortran

Hello

I have a fortran dll with a large number of functions receiving character strings as arguments

for example

double precision function func(str1,prop1,prop2,str2) BIND(C,name='cppfunc')

use, intrinsic :: ISO_C_BINDING

!DEC$ ATTRIBUTES DLLEXPORT :: func

implicit none

!define input variables

character, dimension (12), intent(in) :: str1

character, dimension(255), intent(in) :: str2

..

additional processing

on the c++ side I declare a function

extern "C"

{

link error

Hello I have upgraded to the new version of the compiler and I am getting the following error

1>LINK : fatal error LNK1104: cannot open file 'libmmdd.lib'

I am using Intel(R) Visual Fortran Compiler XE 15.0.3.208 both in 32 and 64 bit

any help would be welcome

best

jac

 

values of parameters in ENTRY

Working with :

============================================================

1>------ Build started: Project: Xdsim10, Configuration: Debug Win32 ------

1>Compiling with Intel(R) Visual Fortran Compiler XE 15.0.1.148 [IA-32]...

================================================================

in Visual Studio Professional 12 - Update 4.

In debugging, values of parameters passed in ENTRY statements are not displayed.

Quick watch notification is : 'undefined variable' or something like that.

Strategies for Battery-Friendly Intel® RealSense™ Applications

For mobile platforms that run on battery power, the longer the device can run between charges, the more desirable the user experience. This paper presents several techniques for developing power efficient applications using the Intel® RealSense™ Software Development Kit (SDK), primarily targeting battery-powered devices such as laptops and tablets.
  • Entwickler
  • Microsoft Windows* 10
  • Microsoft Windows* 8.x
  • Spieleentwicklung
  • Intel® RealSense™ Technologie
  • Windows*
  • C/C++
  • Intel® RealSense™ SDK
  • Intel® RealSense™ Technologie
  • Intel RealSense
  • Intel RealSense SDK
  • improve power efficiency of applications
  • Benutzererlebnis und Design
  • Compiler errors with parameterized types using defined assignment and - operator

    module TestParamTypeMod
       integer, parameter :: DP =  SELECTED_REAL_KIND(13)
       
       type DoubleDif(n)
          integer, len :: n
          real(DP) :: v
          real(DP) :: d(n)
       end type
       
       interface assignment(=)
          module procedure ass_D_Dpdif, ass_Dpdif_Dpdif
       end interface
       
       interface operator(-)
          module procedure sub_Dpdif_Dpdif
       end interface
       
    contains
    
    pure elemental subroutine ass_D_Dpdif(b, a)
       real(DP), intent(in) :: a
       type(DoubleDif(*)), intent(inout) :: b
       b%v = a
       b%d = 0.0_DP
    end subroutine
    

    Character String Length Problems

    To the Intel Forum,

    I'm converting a Compaq Fortran code to compile and run under Intel Fortran XE 2013 SP1 (M/S Windows 7)  However, I seem to be having some very basic Character String length problems when using the debug tool under Intel Fortran 2013. For example:

    CHARACTER ACS*5, NAME*10

    ACS = 'Pitch'

    give an error, or even inserting a character from one string into another with I=3,

    WFILE(1:1) = NAME(I:I)

    also generates an error under Debug step through.

    Q about debugging difficulty

    I am debugging a program, and I get a breakpoint, apparently because of an out-of-range subscript.

    Anyway, when I open the relevant subroutine, isn't it supposed to SHOW me where the breakpoint occurred?

    (It is mentioned in the OUTPUT pane.) but it doesn't show me where in the CODE listing.

    I also wanted to put the cursor on some variables that would show me their contents

    so I can track down why it occurred. But I don't get anything regarding what is stored in any of them.

    Microsoft Windows* 8.x abonnieren