Program Initialization and Source Extensions
Source video: FORTRAN in 100 Seconds (Fireship, 2:38) · at 01:00. The video says to use a file that ends in f or f95. It says wrongly that the suffix selects the version.
Parent section: Technical Evaluation of Video Content and Syntactic Mechanics
Contemporary Fortran applications encapsulate core executable routines inside formal blocks demarcated by the program declaration and terminated by end program7. The video illustrates code using the .f95 file extension7. Within professional engineering environments, using .f95 is an uncommon convention7. Free-form source code across all contemporary standards (including Fortran 90, 95, 2003, 2008, and 2018) standardized almost universally around the .f90 extension1. The older .f or .for extensions are reserved for legacy fixed-form code7. Relying on .f95 introduces practical compilation issues, as certain established compiler suites, such as legacy releases of Intel’s ifort, fail to automatically recognize .f95 as free-form source without explicit CLI override flags7.
Review findings for this part
Section titled “Review findings for this part”The findings come from ../../findings/ (pass 1). The script matches them to this part by source line.
| ID | Severity | Evidence | Status | Location | Problem |
|---|---|---|---|---|---|
| D07-C1 | critical | DOC | open | L5-89, L93, L98 | Claim: The superscript numbers cite sources for each sentence.. Problem: The citations do not support the text. Source [1] is a Facebook group post about formatted input and output. The report cites it about 15 times for history, uppercase letters, character sizes, functions, intent and coarrays. Source [6] is a Hackaday article. The reviewer read it (WebFetch). It does not discuss card columns, keypunch models or errors in the video. But the report cites [6] for these (L11, L15, L20, L53). |
| D07-M5 | major | VIDEO VERIFY | verify | L28 | Claim: .f95 is uncommon. Use .f90 for free form. Old ifort releases do not accept .f95.. Problem: The advice is correct and useful. The forum thread [7] says the same. But the video says that the suffix selects “a certain version like Fortran 95” (01:04 to 01:07). The report does not correct this. In gfortran, the suffix selects fixed or free source form. The flag -std= selects the standard. The ifort detail has no real source. |
Review worksheet
Section titled “Review worksheet”1. Goal of this part
Section titled “1. Goal of this part”What does this part try to show, or help the reader decide?
2. Key claims to test
Section titled “2. Key claims to test”| # | Claim | Evidence given (citation / data) | Verifiable? |
|---|---|---|---|
| 1 |
3. Adversarial review
Section titled “3. Adversarial review”- Strongest counter-argument:
- Unsupported, overstated, or outdated claims:
- Source quality (primary vs. blog/forum/marketing):
- Omissions / what a skeptic would ask:
- Internal consistency with other segments:
4. Evaluation
Section titled “4. Evaluation”- Does the segment achieve its goal? (Yes / Partly / No)
- Confidence: (High / Medium / Low)
- Required fixes: