@richardsymonds: "I am new to this group and looking for a charter or description of what is 
welcome and not welcome here.  My questions will be very specific, but 
probably very elementary, and this may not be the appropriate venue.  I 
learned my FORTRAN a long time ago, but until recently have only used it in 
console mode and with very little more advanced than what I learned way back 
then.
Is there a better place for me to participate?  For example, today I 
realized that a "C" in column 1 is not recognized as a comment in F90.  Had 
me baffled for about 10 minutes until I stumbled across the answer in an 
online manual.
Thank you.
Rich "
    @dpbozarth: "<quote>
No...this is the place for Fortran-related stuff...
That's not <quite> correctit isn't exactly F90, it's free source form
as opposed to fixed source form although free source form was introduced
in F90.  You can write F90/95-compliant Fortran in traditional fixed
format source form.  (Although I think the free source form is much more
readable in general)."
    @nospam: "<quote>
As Duane says, this is the place for Fortran questions. We see all kinds 
of levels of question here, from the most elementary, to ones that stump 
the experts.
There are some kinds of questions that are better directed at specific 
vendors - things like installation or other support issues with a 
particular vendor's product. People will often try to answer those here 
anyway, but sometimes you really need to go to the vendor. The group 
tends to stick more with questions about the language in general; that's 
not a hard "rule" - exceptions abound, but it is the general tendency.
And sometimes there are things that are better done by reading in a 
textbook, either because the matters require more elaboration than is 
likely to be put in a message here, or because a series of questions 
about the same area suggests that it would be better to learn the 
underlying principles instead of just single-point answers.
Ask away."
    @dpbozarth: "<quote>
It's there, just a little hard to find amongst all the other trees... :)
Under Project/Settings select the source file in the project tree.  Then
in the Fortran tab there's a setting for Source Form.  That will be
specific to the single file if you have mixed.
If you select the Project instead of a single file, then you get
additional pages in the settings dialog, but under Fortran there's the
same choice of source form which can be made global to the project.
These can be changed ad hoc w/o creating new projects, etc., ..."
    @jdujic: "| Thanks for the help and the welcome.  I am working with Compaq Visual
| Fortran 6.6a inside developer studio.  I had the .F90 and changed it to
| .f and was able to retain "C" in column one rather than replace with
| "!".  I could not just rename but had to create a new workspace and new
| project with the correct properties.  Possibly overkill, but I could
| find no way to change those properties.  (Yes, I am new to the
| develepor studio also, and I will likely be moving over to .NET and a
| different Fortran compiler in the future.)
You can't change the properties of an existing file within the project,
but you can:
* delete the old one by hitting "Del" in FileView
* add new one(s) by 
  - right-clicking the project in FileView and selecting 
    "Add Files to Project"
  - using Project/Add to Project/Files...
The "folders" within FileView are purely virtual, i.e. they can help
you logically group the source files, but you cannot add an existing
file system folder to it (directory).
 Jugoslav
___________
<url>
Please reply to the newsgroup.
You can find my real e-mail on my home page above."
    @dpbozarth: "<quote>
...
You don't need to change the properties of the file itself, simply apply
the compiler options to the specific file(s) or the project
generically.  This is done by either selecting individual files or the
project in the source tree in the project settings dialog."
    @jdujic: "|| 
||| Thanks for the help and the welcome.  I am working with Compaq Visual
||| Fortran 6.6a inside developer studio.  I had the .F90 and changed it to
||| .f and was able to retain "C" in column one rather than replace with
||| "!".  I could not just rename but had to create a new workspace and new
||| project with the correct properties.  Possibly overkill, but I could
||| find no way to change those properties.  (Yes, I am new to the
||| develepor studio also, and I will likely be moving over to .NET and a
||| different Fortran compiler in the future.)
|| 
|| You can't change the properties of an existing file within the project,
|| but you can:
| ...
| 
| You don't need to change the properties of the file itself, simply apply
| the compiler options to the specific file(s) or the project
| generically.  This is done by either selecting individual files or the
| project in the source tree in the project settings dialog.
Learn something new every day... I didn't know it was possible in this way.
However, changing the source form for the extension is IMO a recipe for
confusion. It's easier to conform to the de facto standard (.f90 for
freeform, .for or .f for fixed-form) than to port to other compilers and
fiddle with compiler options. And this is only the most trivial example.
 Jugoslav
___________
<url>
Please reply to the newsgroup.
You can find my real e-mail on my home page above."
    @dpbozarth: "<quote>
...
...
In general I can't argue w/ that, Jugoslav... :)
But, in defense of this alternative for such items, if one is building a
project in the IDE, it all gets handled there "automagically" so it
becomes essentially a part of the project definition.  It has always
seemed to me that there is sort of an implicit implication that if one
is building a project in CVF using VS that wide-spread porting isn't a
priority."
    @dpbozarth: "<quote>
...
...
Not a bad suggestion other than I suspect at that point Richard didn't
really know there was much specific to the compiler in the
question/comment... :)
And, in reality, the question as posed was pretty much generic to all
F90 compilers.  It was only when responders addressed the specific
compiler/IDE in followups did it really become CVF-specific."
    @jdujic: "|| 
| ...
|| Learn something new every day... I didn't know it was possible in this way.
|| 
|| However, changing the source form for the extension is IMO a recipe for
|| confusion. It's easier to conform to the de facto standard (.f90 for
|| freeform, .for or .f for fixed-form) than to port to other compilers and
|| fiddle with compiler options. And this is only the most trivial example. ...
| 
| In general I can't argue w/ that, Jugoslav... :)
| 
| But, in defense of this alternative for such items, if one is building a
| project in the IDE, it all gets handled there "automagically" so it
| becomes essentially a part of the project definition.  It has always
| seemed to me that there is sort of an implicit implication that if one
| is building a project in CVF using VS that wide-spread porting isn't a
| priority.
In general I can't argue w/ that, Duane... :-)
Take myself for an example :-). Although I do advocate following the
standards as much as possible, I mostly don't practice what I preach;
I unhumbly consider myself as a "Master of Tweaks in VF". 
 Jugoslav
___________
<url>
Please reply to the newsgroup.
You can find my real e-mail on my home page above."
    @dpbozarth: "<quote>
Not unless you know for sure it is compiler-specific would I say that
was necessaryand "thread drift" is a fact w/ usenet and as to this
particular thread, it remained directly on the issue.
In fact, I pointed out that the original question/comment wasn't
compiler-specific at all, but a general feature of F90 compilers.  It
makes no sense to be so topic-conscious (and clf isn't, anyway, in
general) as to expect to move to another forum to follow up on an
original post w/ some compiler-specific info.
For one thing, another long-time participant and CVF user learned
something he didn't know, an always useful side effect.... :)"
{'source': 'USENET', 'other_information': '{"reply_count": 10, "forum_name": "comp.lang.fortran.20140807.mbox"}', 'file': 'data/output/usenet-comp.lang.parquet'}