When I open a project in Visual Studio, what controls the "initial item"? I have one project which, most of the time but not always, the working item display tries to open a static library item that is a part of the project (and shows as such in the Solution Explorer window) Of course this item contains only object code, so the working window shows only binary stuff in Hex. This has become quite annoying. If I switch to display a source code item and then close VS, the next time I open the project it will start with that item--as I would expect--but this behavior does not stick.
I originally posted this question on Stackoverflow (http://stackoverflow.com/questions/30823756/invoking-constructor-of-abst...), but perhaps the Intel community har more knowledge on this topic?
Consider one of the classic OOP examples (see source code at the end of the post):
- Abstract base class Shape
- Class Rectangle extending Shape
I have two questions:
I have been liberally using non-signalling nans as a debug aid. I can use these anywhere an initialization expression is allowed. But having no signalling limits the usefulness of this method.
I tried to make use of the new option Qinit:snan but that is only applicable to local scalars which are a small subset of the cases I need.
I create a parameter for my initialization like this:
real(DP), parameter :: aNaN = 0.0D0 / 0.0D0.
and declare arrays within derived types like this:
Compiling this program with ifort version 15.0.1 gives me:
testarray.f90: catastrophic error: **Internal compiler error: segmentation violation signal raised** Please report this error along with the circumstances in which it occurred in a Software Problem Report. Note: File and line given may not be explicit cause of this error.
compilation aborted for testarray.f90 (code 1)
Here is the code:
When using shift-control-f to search an entire solution, is it possible to ignore comments?
Also, where is shift-control-f located on the pull down menu of Visual Studio 2012?
Consider the following simple code snippet. Intel Fortran does give a warning if the procedure does not give a value to a dummy argument with an explicit INTENT(OUT) attribute. However a warning if such a variable is used before being defined is missing; it'll be very helpful if the compiler can warn for this situation as well.
I have inherited this code and when I try to compile it I get the following error. Being a newbie to Fortran 90 I would appreciate any help
When I compile this code I get the message - do-variable within a DO body shall not appear in a variable definition context. I presume this code did compile with pgf90 (that is what the author of the code told me) but I am not sure why it does not compile with ifort.
I am looking for Intel Fortran Composer XE 2011 SP1 Update-4 version. I had a student version of latest 2015 version and was just trying to download older version from additional downloads.
I have two queries;
I downloaded the trial version of Intel Parallel Studio XE 2015 Cluster version. It's the update 4 version. And I tried to install it in my computer. However, after I installed it, it only shows some documentations. I couldn't find the tools folder. So I can't use Intel fortran compiler. I wonder what I can do about it. Is this because I am using the trial version?
Thank you so much.
I have some mixed C/Fortran code in VS2010. I get different results from the 32-bit and 64-bit builds of the code. To see if it is a precision problem, I would like to compile the 64-bit build with a switch that forces the real and integer variables to be single precision (4-bytes). Are there switches for the C and Fortran compilers to do this? Please let me know. Thank you.