Prev: FCC VAX VMS Fortran program AMDIST
Next: Intel Fortran
From: rfengineer55 on 10 Jun 2010 09:35
<<<Sometimes. Do note that using nonstandard syntax is a way to
signicantly
increase the frustration part. Some of us learned that lesson a long
time ago. (See the quote in my signature). Yes, I realize it wasn't
you
who wrote the nonstandard syntax; you just get to pay some of the
cost
in frustration.

I did spend a little time looking at this code, but decided it was
too
much fuss to look further, at least for tonight. I first took out a
large number of line wraps (mostly from comments) introduced either
by
your usenet posting software or my usenet reader (I'm not actually
sure
which). Easy, if a bit boring because of the large number. I noticed
the
reference to a missing include file, but figured I might be able to
ignore that (though there is at least a possibility that the error is
in
the include file or related to it). >>>>

OK,

First, huge note of thanks to the responder who found the downloadable
DEC documentation. I just got up this AM and have not had a chance tom
download it yet, but thanks for looking, and checking that out for
me.

First I do not have any posting software over and above what this list
provides for posting a new message. I am saddened to learn that there
were word wrap issues when the source code posted. I also do not have
any brand of USENET software.

In my related post elsewhere, I asked for the procedure to put my
Intel Visual Fortran into the VAX VMs mode, and I had no t\akers to
tell me how to do that. I have posted that request at the Intel forum,
over 35 people have read it, nobody has responded.So I think I have a
reason to be frustrated. My 18 year old Microsoft Fortran has VMS
extension mode, and it is not a branch of rocket science to implement
it.

Thank you for the huge effort that you nfolks took by looking over the
source code that I posted. I'm sorry that it turned out being an added
pain in the neck due to the word wrap thing.

The Mkeys.for deletion problem would not have come home to roost until
those two errors are cleared up. the compiler is funny that way. You
think you have ths source all cleared up and. OH BTW, here are some
OTHER things wrong with your code.

What will help a great deal is, a document to translate the difference
in extensions or dialects between VAX VMS Fortran and Fortran 77. I
prefer sticking with Fortran 77 because I have compilers that can
handle it, and it would be a huge project to convert these FCC
programs to Fortran 2003. It would also be profoundly unneccessary.
All I ultimately need is an exe file that will run on my computer. The
end product does not have to be fashionable

Jeff
RF ENGINEER55


From: Les Neilson on 10 Jun 2010 10:19

"rfengineer55" <rfengineer55(a)aol.com> wrote in message
news:9f6ed9ea-d76f-464f-81cd-bc3bcf864653(a)w31g2000yqb.googlegroups.com...

<snip>
>
>
> In my related post elsewhere, I asked for the procedure to put my
> Intel Visual Fortran into the VAX VMs mode, and I had no t\akers to
> tell me how to do that. I have posted that request at the Intel forum,
> over 35 people have read it, nobody has responded.So I think I have a
> reason to be frustrated. My 18 year old Microsoft Fortran has VMS
> extension mode, and it is not a branch of rocket science to implement
> it.

Did you not see the reply on this group from Steve Lionel ? In particular :

"In most cases you don't need to do anything - Intel Fortran accepts
almost all of the Fortran extensions that VAX Fortran had. Some
exceptions are RADIX50 constants and intrinsics, and indexed
organization files. As others have said, there is a /vms option which
changes some defaults to be even more compatible with the VMS compilers
- adding support for octal constants using " syntax, for example."

Also there have been a number of replies on the Intel Forum - note some of
us keep different hours to Illinois ;-) and not all of us know about the
VMS "dialect".
By dialect you really mean the Extensions to Standard F77 provided by the
VAX compiler, that the code makes use of.
Extensions can be notoriously non-portable. Fortunately Steve has indicated
the the Intel compiler should be ok - in priciple - with this code.
(and some of your difficulty is in how to use the Visual Studio environment
for development of the software - some replies (including my own) on the
Intel Forum have attempted to help you there)

We will help in whatever way we can if you provide specific examples of the
errors *and* the appropriate code.
Might I suggest that you compile the code one routine at a time that way the
errors are more manageable.

Les

From: Steve Lionel on 10 Jun 2010 10:40
On 6/10/2010 9:35 AM, rfengineer55 wrote:

> In my related post elsewhere, I asked for the procedure to put my
> Intel Visual Fortran into the VAX VMs mode, and I had no t\akers to
> tell me how to do that. I have posted that request at the Intel forum,
> over 35 people have read it, nobody has responded.So I think I have a
> reason to be frustrated. My 18 year old Microsoft Fortran has VMS
> extension mode, and it is not a branch of rocket science to implement
> it.

You posted in our user forum yesterday at 7:47PM ET and had a response
to your specific question just a few hours later. I'm not sure I
understand what your expectations are.

As I indicated in a group posting yesterday, it is usually not required
to "put the compiler in VMS mode", and nothing I have seen here so far
would require that for your code.

I understand that you are frustrated, but people have been helping you.

You commented also on "the posting software this list provides". This
list provides no posting software. You are using Google Groups which has
some issues with how it formats posts.

--
Steve Lionel
Developer Products Division
Intel Corporation
Nashua, NH

For email address, replace "invalid" with "com"

User communities for Intel Software Development Products
http://software.intel.com/en-us/forums/
Intel Software Development Products Support
http://software.intel.com/sites/support/
My Fortran blog
http://www.intel.com/software/drfortran
 | 
Pages: 1
Prev: FCC VAX VMS Fortran program AMDIST
Next: Intel Fortran