Prev: Why was SPREAD left out of initialization expressions?
Next: Compile and link optimization using gfortran
From: Mike Prager on 21 Jun 2010 13:59
On Sun, 20 Jun 2010 16:59:04 -0400, "e p chandler" <epc8(a)juno.com>
wrote:

>This program works for me on Vista (32 bit). Just retrieve the command line
>or a command line argument.
[...]
>Now when I drag and drop "foo.dat" onto "a.exe" here is what I see in the
>console window:
>
> |C:\Users\epc\Desktop\a.exe C:\Users\epc\Desktop\foo.dat |
> 55 0
>PAUSE statement executed. Hit Return to continue
>
>I don't know if this works on XP or earlier.
>

Elliot,

THANKS! I thought I had tried this, but I must have done something
wrong, as I tried again, and it works fine under XP and Windows 7. To
get the PAUSE without adding it to the Fortran program, I just used a
batch file:

@echo off
@aspic.exe %1 %2
@pause

This is an easy, cheap, effective solution to the problem -- the kind
I like.

Mike
From: Gordon Sande on 21 Jun 2010 14:01
On 2010-06-21 14:41:47 -0300, Mike Prager <mprager(a)3.14.alum.mit.edu> said:

> On Sun, 20 Jun 2010 19:27:09 -0500, "Gary L. Scott"
> <garylscott(a)sbcglobal.net> wrote:
>
>>> On Sat, 19 Jun 2010 23:39:36 +0000 (UTC), David Duffy
>>> wrote:
>>>
>>>> Mike Prager<mike.prager(a)mhprager.com> wrote:
>>>
>>> The special Windows requirement is to be able to drag and drop a data
>>> file onto the program icon to cause the program to analyze the data
>>> file. That doesn't work with console programs, at least any way I've
>>> tried. It does work with QuickWin or VSW. It's needed for teaching
>>> undergrads, for most of whom a command prompt is a foreign concept.
>>
>> Gino can do that and is one of the easiest to program.
>
> Yes. It's also US $3600!

Depends on how you price out various budget lines. :-) Sometimes
manhours are worth almost zip and sometimes cash it very expensive
compared to nominal values.



From: GaryScott on 21 Jun 2010 16:03
On Jun 21, 12:41 pm, Mike Prager <mpra...(a)3.14.alum.mit.edu> wrote:
> On Sun, 20 Jun 2010 19:27:09 -0500, "Gary L. Scott"
>
> <garylsc...(a)sbcglobal.net> wrote:
> >> On Sat, 19 Jun 2010 23:39:36 +0000 (UTC), David Duffy
> >> wrote:
>
> >>> Mike Prager<mike.pra...(a)mhprager.com>  wrote:
>
> >> The special Windows requirement is to be able to drag and drop a data
> >> file onto the program icon to  cause the program to analyze the data
> >> file. That doesn't work with console programs, at least any way I've
> >> tried. It does work with QuickWin or VSW. It's needed for teaching
> >> undergrads, for most of whom a command prompt is a foreign concept.
>
> >Gino can do that and is one of the easiest to program.
>
> Yes.  It's also US $3600!

When only the best will do :). Upgrades are much more reasonable (so
there's good news if you become hooked). And they work very hard to
add the most requested features and fix bugs. I've gotten virtually
every feature I ever asked for save for a few, e.g. 1) improved RTF
editor (it uses the basic one MS distributes for the less capable
editors like MS Outlook), 2) improved WEB support (I'd like to program
entirely in GINO and have them output web-compatible streams (html,
svg, png)...although they've recently added Flash support, so maybe
there's hope), two built in tools: a font editor (mainframe package
came with this) and a help editor (cross platform)
From: e p chandler on 21 Jun 2010 16:04
On Jun 21, 1:59 pm, Mike Prager <mpra...(a)3.14.alum.mit.edu> wrote:
> On Sun, 20 Jun 2010 16:59:04 -0400, "e p chandler" <e...(a)juno.com>
> wrote:
>
>
>
> >This program works for me on Vista (32 bit). Just retrieve the command line
> >or a command line argument.
> [...]
> >Now when I drag and drop "foo.dat" onto "a.exe" here is what I see in the
> >console window:
>
> > |C:\Users\epc\Desktop\a.exe C:\Users\epc\Desktop\foo.dat         |
> > 55 0
> >PAUSE statement executed.  Hit Return to continue
>
> >I don't know if this works on XP or earlier.
>
> Elliot,
>
> THANKS!  I thought I had tried this, but I must have done something
> wrong, as I tried again, and it works fine under XP and Windows 7.  To
> get the PAUSE without adding it to the Fortran program, I just used a
> batch file:
>
> @echo off
> @aspic.exe %1 %2
> @pause
>
> This is an easy, cheap, effective solution to the problem -- the kind
> I like.
>
> Mike

Note: Spaces are legal in Windows pathnames. So I would look at the
entire command line instead of the Fortran equivalent of argv[].

--- E
From: Philipp E. Weidmann on 22 Jun 2010 02:30
Mike Prager wrote:
> I am in the market for a single copy of a commercial* Fortran compiler
> to use under Windows. I'm seeking advice on the options.
>
> Because I am a one-man, part-time consulting shop, price is important.
> Lahey Express is cheap, but apparently it's not being updated any
> more. Intel and Absoft both seem good and current. Absoft is a bit
> cheaper, and from what I can see, it is fast and complete. However,
> its diagnostics aren't so great. On the other hand, its IDE was
> designed for Fortran, which would be a pleasant change -- I don't much
> care for Visual Studio.
>
> Any comments on these or other suitable compilers -- including
> comments on tech support -- would be helpful. Feel free to send them
> by email if you would rather comment privately.
>
> Thanks!
>
> Mike Prager
>
> * I am looking only at commercial products because none of the free
> versions has an option (like Lahey's vsw or Intel's QuickWin) that
> makes a simple Windows program without coding changes. If I'm wrong
> about that, it would be great to know it. I have considered using
> DISLIN's widget routines, but that is a much more complex approach.



I use Intel myself, and find it a very good compiler with many
diagnostic options. On Windows, it comes with an IDE based on Visual
Studio which tightly integrates with the compiler, exposing all switches
directly through the GUI.

However, I also like gfortran a lot, and the truth is that this free and
open source compiler is probably sufficient for almost all projects,
commercial or otherwise. One strong point of gfortran is the ability to
use the C preprocessor of the GNU Compiler Collection in your Fortran
projects, which can be *very* useful.

--
-- Philipp Emanuel Weidmann
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5
Prev: Why was SPREAD left out of initialization expressions?
Next: Compile and link optimization using gfortran