Hi,

I heard there two ways to compile files in Compaq Visual Fortran90.
The default setting is Debug. The other one is called Release. It's
said the latter one is faster. But I don't know to choose that option
(in the menu of Compaq Visual Fortran).

Does anyone know where I can find this option? Thanks a lot!

John

We have many new activities on the website. PayPal
1st: Integral
1、From July 1st to August 31, all the registered members will get a
free 100 points integral.
2、As long as you pay for your orders, you will be presented with
the same amount of integral. For

example, if your order’s amount is $ 100, then you will get 100 points
integral
3、Every time after you place the orders, you can use your points to
exchange our company’s gift

and we will send them together with your parcel.
4、The integral decide the different grades of the members., and the
different members will enjoy

Dear all;

I'm gonig to use FFTW libraries in order to calculate the 3D-FFT of a
step function.
I defined the 3D step function on a 100*100*100 mesh.
then I installed fftw-3.1.2 package (fftw-3.1.2.tar.gz), but I don't
know how can I use it?
Please let me know if there is anyone that can help me.

I'm anxiously looking forward your reply and guidelines.

With my best regards,
Fatemeh

Hi,

I am maintaing legacy code that calls Fortran from C. I have a
problem with the mismatch between C and Fortran string delimiter/
length handling, so when Fortran tries to execute
"read(passedstring,*) param,..." it fails because of the extra "noise"
in the string (the null value and following memory).

However, this code used to work with g77. The C code is given below,
and I am working on Linux (so _LINUX is defined). The fortran being
called looks like:
subroutine hypo_ew( strn, iresr )
character*80 strn
integer*4 iresr
...

So it seems that the code used to pass in a length as the third
argument to this function, and that length was taken as the length of
the first argument (character array). This no longer seems to happen,
although it does link and run ok (using -ff2c).

For extra fun I am on 64bit using -m32 and when this code worked with
g77 it was on "real" 32bit.

G'day everyone

In the code below everything is ObjectData %% this and ObjectData %%
that. Aside from putting stuff in locally scoped variables, is there
any way of specifying a context for symbols, so that I don't have to
keep typing ObjectData %% ?

Kind regards,
Bruce.

CASE (WS_2D1 : WS_2D2 )
y = JMOD( ObjectData %% aCursors( ObjectData %% nWorkspace ),
ObjectData %% aDims( ObjectData %% nWorkspace ) %% cols )
x = ( ( aCursors( ObjectData %% nWorkspace ) - y ) / &
ObjectData %% aDims( ObjectData %% nWorkspace ) %% cols ) + 1
ObjectData %% aCoords( ObjectData %% nWorkspace ) %% x = x
ObjectData %% aCoords( ObjectData %% nWorkspace ) %% y = y

http://blogs.siliconvalley.com/gmsv/2008/06/one-more-for-the-gates-legacy-book-there...
One more for the Gates legacy book: “There are work-arounds, use
those.”
Posted by John Murrell on June 26th, 2008 at 10:23 am | Categorized as
Uncategorized

Spurred by the outpouring of Bill Gates retrospection on the eve of
his departure from Microsoft (see “How many times have you wanted to
send a memo like this to Bill Gates?“), faithful reader Bill Terrill
was kind enough to share this story from back in the day:

“Ah, how I wish I had known — I could have recorded my ‘discussions’
with Bill Gates back in 1979/80. I was with Zilog at the time as a
development manager. I had a couple of groups working for me at the
time — compiler development (Programming Language Zilog — PL/Z) and
Operating System Support. Our operating system was a variant of CPM
(call RIO) and we had gotten a big contract from the U.S. military
(over $5,000,000!) for our Z80 systems with a Fortran compiler. Since
we didn’t have a Fortran compiler of our own, someone decided to
purchase one from an outside firm. That firm was Microsoft.

ALL,
I define a data type as:

TYPE TENSOR
REAL(DP)::T0
REAL(DP),ALLOCATABLE,DIMENSION(:) :: T1
REAL(DP),ALLOCATABLE,DIMENSION(:,:) :: T2
REAL(DP),ALLOCATABLE,DIMENSION(:,:,:) :: T3
REAL(DP),ALLOCATABLE,DIMENSION(:,:,:,:) :: T4
REAL(DP),ALLOCATABLE,DIMENSION(:,:,:,:,:):: T5
END TYPE

Define variable and allocate as

TYPE(TENSOR):: S,Y,Z,X,W

CALL ALLOCATE_NTUPLE( S ); S = ZERO
CALL ALLOCATE_NTUPLE( Y ); Y = ZERO
CALL ALLOCATE_NTUPLE( Z ); Z = ZERO
CALL ALLOCATE_NTUPLE( W ); W = ZERO
CALL ALLOCATE_NTUPLE( X ); X = ZERO

Y=3.0D0 !overloading works
W=4.0D0*Y !!!!Never get past here!

HAI..........
Guys this web site s very useful to
you...........
How This site
helps..........
how to earn money form
online......
In this site, you wil earn more than 10000/- Rs per month....
its true ....... just login this site and << EARN MONEY

www.freeonlinedollers.blogspot.com

www.freedollers.blogspot.com

www.moviesgossips.blogspot.com

HAI..........
Guys this web site s very useful to
you...........
How This site
helps..........
how to earn money form
online......
In this site, you wil earn more than 10000/- Rs per month....
its true ....... just login this site and << EARN MONEY

www.freeonlinedollers.blogspot.com

www.freedollers.blogspot.com

www.moviesgossips.blogspot.com

Hello all,

I have Fortran (90) code which I want to use in IDL. I use IDL's
Call_External function and I want to pass some variables by reference.

I write the Fortran file

Subroutine main(argc,argv)

Implicit None
Integer :: argc,argv(*)
...

Call Do_Something(%%val(argv(1)),%%val(argv(2)),..) ! Changes the
values of my arguments
! That is nice, because this way I can pass tons of data from
Fortran back to IDL

End

Subroutine Do_Something(....)

Implicit None

...

End

And I make a shared object file with the -shared flag at the Fortran
compiler