Re: Encapsulation

Arne Vajhøj wrote:
Jon Harrop wrote:
Absolutely. Many of our competitors are bumbling around with enormous
Fortran 77 codebases that have no encapsulation or high-level structure
at all.

Tolerating the same deficiencies would mean commercial suicide for us.

I was talking about .NET code even though I also know about
some Fortran code.

But one size does not fit all. Maybe C# and .NET is not
suitable for your apps.

Fortunately there are other .NET languages. Unfortunately, the all share
deficiency AFAIK...

--
Dr Jon D Harrop, Flying Frog Consultancy
http://www.ffconsultancy.com/products/?u
.

Relevant Pages

  • Re: communicating the name of a function to deep within the call tree
    ... it separates parts of two thirds, unless it really isn't two thirds. ... If Fortran had RATIONAL as a data type, ... generic programming. ... no deficiencies and the other way is to make it so complicated ...
    (comp.lang.fortran)
  • Re: F08 support of floating decimal?
    ... base 3 floating point is also rare. ... Legal for Fortran, though. ... trinary (where the digits are zero, one, and minus one) ... no deficiencies and the other way is to make it so complicated ...
    (comp.lang.fortran)
  • Re: C style compound assignment operators
    ... In C and C++ they are either prefix or postfix, ... Remember that Fortran has a source form in which spaces ... no deficiencies and the other way is to make it so complicated ...
    (comp.lang.fortran)
  • Re: Logicals converted to integers during reading
    ... This will also happen in Fortran versions that allow logical operators ... compliant implementations to detect and report. ... Fortran should *never* allow mixed-mode operations between ... no deficiencies and the other way is to make it so complicated ...
    (comp.lang.fortran)
  • Re: Fortran Question
    ... >> is there a possibility to reextract the fortran code out of the ... there is no possibility to disassemble Fortran object code. ... via the net code, ...
    (comp.lang.fortran)