Skip to content

FORTRAN Newsgroup

Home arrow Computational arrow FORTRAN arrow FORTRAN Newsgroup


FORTRAN Newsgroup
Discussion about FORTRAN.

  • Re: fortest.f90
    [explains the usual issue with Fortran/C character passing]
    Except that I think you'll find that won't work because my tcp_write
    expects msglen to be passed by address instead of by value as will
    probably happen with most implementations (as you correctly describe).
    This is intentional. The documentation I provided in the post was

  • Re: fortest.f90
    There is an interfacing problem here:
    In calls like:
    call tcp_write(sock,msg,msglen,erro r)
    the argument msglen is not needed. The C source does define it, but
    that
    is because most Fortran implementations pass the length of a string as
    a hidden argument. This argument is visible on the C side, but it is

  • Re: fortest.f90
    I have installed the equation.com version of gfortran and it comes
    with the
    libws_32.a library, alright. But perhaps not the very latest
    version ...
    Regards,
    Arjen

  • Re: Web site and Workshops
    Uno wrote:
    Sorry, dont comprehend the Linux world... :)

  • Re: Web site and Workshops
    After rereading this, it reads a little more snotty that I intended.
    Add a few ";)" here and there and it reads better!
    Dick Hendrickson
    PS: Even with a ;) I still don't like *nix :(

  • Re: fortest.f90
    Uno wrote:
    Did you install MinGW?
    I've installed both mingw-4.4 and mingw64-4.5. In the 32-bit installation
    libws2_32.a is in mingw-4.4\lib, while in the 64=bit version it's in
    mingw64-4.5\x86_64-w64-mingw32 (unless I've made a typo). My gfortran is
    installed as part of mingw64-4.5.
    BTW I'm using Code:Blocks as the IDE, and I guess it's smart enough to find the

  • Re: Web site and Workshops
    Ich kapiere nicht.
    $ pwd
    /home/dan/.mozilla/firefox
    $ ls *
    profiles.ini
    vkuuxfit.default:
    blocklist.xml extensions.ini search.sqlite
    bookmarkbackups extensions.rdf secmod.db
    bookmarks.html formhistory.sqlite sessionstore.bak
    Cache key3.db sessionstore.js

  • Re: fortest.f90
    Where did you find that library? This is brand spanking new from
    equation.com, which I thought were mingw-based:
    Dir for this script: C:\eq\source\
    C:\eq\source>dir
    Volume in drive C has no label.
    Volume Serial Number is 942A-AD55
    Directory of C:\eq\source
    09/01/2010 03:35 PM .

  • Re: Web site and Workshops
    Uno wrote:
    I have made fpt clickable to firefox by:
    Open a folder
    click tools
    click folderoptions
    click filetypes
    select (none) URL:file transfer protocol
    and with the advanced button assign firefox to it.
    I guess its the same for mailto: and Thunderbird.
    In my case, I checked and it had TB assigned to it.

  • Af lovers Shirt polo thirt and polo t-shirt CA man long sleeve Shirt DG man long sleeve Shirt
    Shirt and t-shirt
    Af lovers Shirt polo thirt and polo t-shirt CA man long sleeve
    Shirt DG man long sleeve Shirt
    Ed hardy man long sleeve Shirt Ed hardy woman short Shirt
    Hollister man long sleeve Shirt
    [link]
    [link]
    [link]

  • LV man jeans Robin man jeans Rock Republic women jeans True Religion man jeans Versace man jeans
    jeans
    versace AF man jeans Affliction man jeans Armani man
    jeans
    Coogi man jeans DG man jeans Ed hardy man jeans Evisu man
    jeans Hollister man jeans Levis man jeans LV man
    jeans Robin man jeans Rock Republic women jeans True
    Religion man jeans Versace man jeans

  • http://www.tradingspring.com -- gucci handbag hermes handbag juicy handbag lv handbag marc jacobs handbag Miumiu handbag
    handbag
    Adidas handbag armani handbag balenciaga handbag Bally
    handbag boss handbag burberry handbag cartier handbag Chanel
    handbag chloe handbag christian audigier handbag coach handbag
    cosmetic bag d&g handbag
    dior handbag Ed hardy handbag fendi handbag gucci handbag

  • Re: Web site and Workshops
    That would work better in some common browsers/mail readers as
    [link]
    Dan Feenberg

  • Re: Web site and Workshops
    wasn't working with IE 8 before (blank page) but works now.

  • Re: Web site and Workshops
    Hello,
    Thanks for the testing. :-)
    Now if I can just run enough workshops to pay the rent ... ;-)

  • Re: Web site and Workshops
    Dick, we need the full deal:
    [link]
    I swear we had "smart browsers" twenty years ago that would expand this with
    http://
    plus whatever.
    (Works on windows, of course.)
    Sjouke,
    you wouldn't happen to know why thunderbird led me to believe it was
    clickable? It's taken me this long to make the emailto:'s go to

  • Re: fortest.f90
    Wonderful, this looks very promising. The tough part is getting
    started
    with such a programming task, but with these implementations it ought
    to be lighter work. (Will keep you up-to-date as to the progress I
    make
    with it - which may be slow ;))
    Regards,
    Arjen

  • Re: current status of gfortran vs g95
    To get access to module variable, I think you need a fairly recent GDB;
    I forgot whether the support is already available in 7.1 or has been
    added only later - it is definitely in GDB 7.2 (which has not yet been
    released).
    For support to assumed-shape and deferred-shape arrays (and C's variable
    length arrays), you need to use Jan Kratochvil's pathes, cf.

  • Re: Problem with allocate
    [...]
    Now we might be getting somewhere.
    Do you have array subscript bounds checks turned on,
    substring checks turned on,
    and all other checks tuirned on?

  • Re: Web site and Workshops
    Copy/paste worked, doublwe click worked(xp sp3, thunderbird, firefox)

  • Re: Web site and Workshops
    In Dan Nagle:
    [Snip...]
    FWIW...Works fine with Lynx, so it should work with ANYTHING. :)

  • Re: Web site and Workshops
    Worked here w/ Firefox and XP. Thunderbird embeds the url as a link
    when it displays the page but works either that way or by directly
    entering the url...

  • Re: Web site and Workshops
    Hello,
    Try it now. I think I've brought the frames
    up to the latest standard. At least, it works with Safari,
    Firefox and passes the W3C validator.
    Frames were supposed to make things easier. :-)
    [link]

  • Re: Web site and Workshops
    It doesn't come up for me either. I've tried two machines with two
    different state-of-the-art operating systems. I clicked the link,
    cut-and-pasted, and typed it in by hand. All the same result, just
    a blank page. Beats me, I never did trust these computers, especially
    those running OSs from the 70s!

  • Re: Is this a bug?
    Note that, although I agree that 12.4.1.7(1) says nothing about this
    one, I think that mecej4's quote from 9.5.3.4 makes it nonconforming
    because line(1:20) is associated with line (or at least partially
    associated... I didn't check into that particular gritty distinction to
    see whether I think it matters).

  • Re: Web site and Workshops
    Maybe it doesn't act like a link because it isn't one. The site comes up
    fine for me - not that I spent much time perusing it in detail. The "old
    fashioned" ways that involve typing in urls do still work. Or, if one's
    typing is as bad as mine and you worry about being able to type that
    many characters correctly, there is cut&paste.

  • Re: Is this a bug?
    To test Richard's point about concatenation I wrote the following two
    programs,one of which uses the // operator and one concatenates only
    by having a list of two output items. My own advice the other day
    would suggest that the programs may not be standard-conforming,
    because different compilers gave different run-time output. If Richard

  • Re: Web site and Workshops
    The link doesn't fire for me, dan.

  • Re: Problem with allocate
    Unfortunately, that's how it is for a lot of people who write technical
    books for niche markets. Meanwhile, Sarah Palin can't pen a cohesive
    paragraph and has bestsellers.
    I was in Salt Lake City for x-mas, and old friends gave me a glenn beck
    book as a gag gift. It was to be autobiographical. He writes of how

  • Re: fortest.f90
    Should anyone care, here's the comparable stuff I had for my servers. I
    did not port this to Windows, and it hasn't even been used on a wide
    variety of Unix systems - just the few we were using for servers. It
    started out on SunOS 4, ported to Solaris 2, and I think I recall
    experimenting with this on Linux.

  • Re: fortest.f90
    Here is some more C code that I found online, which shows how to handle both
    Windows and Unix environments, and also how to set up a TCP server. I don't
    understand the significance of the Winsock.h/Winsock2.h distinction.
    sockets.c (contributed by ReyBrujo)
    #include
    #include

  • Re: fortest.f90
    That's perfectly OK with me. Maybe next time someone who searches, like me, for
    gfortran and sockets on Windows, will find this. As you point out, it needs to
    be made a bit more general.
    If you felt inspired, you might extend it to handle the server case (just a bit
    more complicated). Like Richard I need only the client at this stage.

  • Re: Is this a bug?
    In article <1jo3af8.153z3dye23q20N%nos... @see.signature>,
    And quite a lot didn't, for very good reasons - many of us didn't
    like the approach taken precisely because it led to that sort of
    thing. The point was that, in the late 1970s, non-transparent
    memory management of the sort that Fortran 90 introduces was a

  • OT.... Re: Is this a bug?
    For some reason the above words make me think of a scene in an old star trek movie (the one where they go back in time
    to the 80's).
    Scottie is sitting in front of an old macintosh (high end back then) and starts talking to it. The present day engineer
    type in the room tells him to use the mouse. So Scottie picks up the mouse and talks to *that*. (hee hee) Eventually he

  • Re: Is this a bug?
    Obligatory xkcd link <[link]>.
    And don't forget to read the mouseover text or you won't understand the
    connection. :-)

  • Re: current status of gfortran vs g95
    A lot of work was put into both GDB and gfortran 4.5.1 to make GDB
    understand Fortran module variables. I can't say I've tested it
    myself, but you may want to give it a try.
    Ciao!
    Steven

  • Re: Is this a bug?
    (snip)
    Thanks for filling in the blanks. Your statement about arguing
    backwards reminded me of my grad school days where I was
    working on some quantum mechanics or EM homework. I
    sometimes knew the answer, but had no idea how to get from
    point A to B. Starting from answer, I could often derive the

  • Re: Is this a bug?
    It seems not to be in Fortran 66, but it is in OS/360 Fortran IV,
    which WATFIV is supposed to be based on. It seems that this
    distinction was not documented, though.

    So:

    1 format(i3,t1,3x,i1)
    -- glen

  • Re: Is this a bug?
    The standard makes that one pretty explicit. The ' 3 7' result would
    violate the standard. At least it would violate any recent ones. I
    wouldn't guarantee f66 (and I don't feel like checking). Heck, I don't
    even recall for sure whether T format was in f66.
    Now X format has some related quirks. I forget whether or not it blank

  • Re: Is this a bug?
    Well, for that matter, there is no such requirement for subroutines
    either. Although subroutine calls are described as first evaluating the
    arguments, there are restrictions on subroutines that effectively allow
    for "lazy evaluation" because you can't tell the difference in legal
    code.

  • Re: Is this a bug?
    ...
    Ok so far.
    That, however, seems like a non-sequitur that has nothing to do with
    what the standard says. The restriction I cite says nothing about being
    pure or not. Users "presumably wanting" something is not a specification
    in the standard. Users want many things that aren't so. Some of the
    wants are quire reasonable things to want; that still doesn't make them

  • Re: Is this a bug?
    (snip)

    Reminds me of a question related to WATFIV many years ago. I believe
    it is not usual to fill the buffer with blanks at I/O initialization,
    and then not copy excess blanks in with format descriptors,
    but it seems that is what WATFIV does. That is, it copies only
    non-blanks to the buffer for I/O list items. The interesting cases

  • Re: Is this a bug?
    <--CUT-->.

    Richard, thanks for your helpful discussion.
    However, I have a remaining doubt. TRIM being an intrinsic function, is
    pure. Therefore, its arguments (only 1 in this case) have INTENT(IN) and,
    presumably, the user wants the function to be evaluated with argument values
    equal to those that existed prior to the execution of this internal WRITE

  • Re: Problem with allocate
    Well nobody pays me royalties!
    Ian

  • Re: Is this a bug?
    (snip)

    No. That might be true for a subroutine call, but this is I/O.
    There is no requirement that trim(line) be evaluated before the I/O
    operation of 7 is done.
    I have seen C code the equivalent of:
    write (line, '(a, 2x, i3)') line, 7
    That is, it depends on the previous contents of line being written

  • Re: Is this a bug?
    Yes. So LINE appears in a variable definition context. Right. But you
    haven't quoted anything that says it is prohibited from appearing in a
    variable definition context. The above just says that there exist some
    such prohibitions, but you haven't cited one.
    ...
    "could be implemented as" doesn't count as a specification of the

  • Re: Is this a bug?
    16.5.7 Variable definition context
    Some variables are prohibited from appearing in a syntactic
    context that would imply definition or undefinition of the
    variable (5.1.2.7, 5.1.2.12, 12.6). The following are the
    contexts in which the appearance of a variable implies such
    definition or undefinition of the variable:

  • Re: Is this a bug?
    I agree that the code is nonconforming, but I don't see what 16.5.7 has
    to do with the question at all. That seems such a distant relation that
    I wondered whether it was a typo for some other section, but I couldn't
    come up with a likely one. The closest thing I can see 16.5.7 saying is
    that appearance as an internal file counts as a variable definition

  • Re: Is this a bug?
    Steve:
    I have only the draft standard, J3/04-007. In that, Section 16.5.7, titled
    "Variable definition context", lists item 7: "An internal-file-variable in
    a write-stmt" as one of the contexts in which the appearance of a variable
    implies definition/undefinition of the variable. The preamble of the section

  • Re: Is this a bug?
    See Section 16.5.7 in Fortran 2003. IMHO, the code is nonconforming.