Re: Delphi - does catastrophe loom ? (long)

>> i suppose this is a as good a place to stop reading as any. where are you
>> getting these ludicrous numbers? 0.02x the speed of Win32 apps? i'm sure
>> i would have noticed that on /some. level during the past years of
>> working in .NET...

> you would if you worked with Matrices 8^) or Arrays.

Hmm. i use arrays all the time - i suppose it's a question of what to do
with them. For example, do you use things like Delphi's SetLength() method,
which hides from you the fact that you're doing something terribly wrong by
making a potentially very costly operation look like something cheap and
common to do?


.

Relevant Pages

  • Re: seeking advice for "translate" Fortran code to Java code
    ... with these features that just don't exist in Java: ... Labeled COMMON blocks Blank COMMON ... Java arrays are always what C would call arrays of pointers ... FORTRAN I/O class that would emulate formatted and binary I/O. ...
    (comp.lang.fortran)
  • Re: zero values on dynamic array
    ... > written using static arrays. ... Perhaps the most common such way is using COMMON. ... awill get you the same memory locations as AA. ... dynamic allocation of the 2 arrays. ...
    (comp.lang.fortran)
  • Re: Question about COMMON
    ... It's not hard to cause these arrays to exceed the available ... > sticking the big arrays in COMMON blocks. ... by shifting these variables to the heap. ... If you are doing OpenMP parallelization of operations on COMMON blocks, ...
    (comp.lang.fortran)
  • Re: C vs. Fortran (half OT questions)
    ... I'd agree it was rare for compilers to check ... most common and least problematic bounds errors. ... But arrays with bounds known at compile time ...
    (comp.lang.fortran)
  • Re: Fortran Standard question: COMMON, SAVE and EQUIVALENCE
    ... Exactly what you did -- you put x into COMMON, then equivalenced other arrays to it that are larger in extent; hence extending the COMMON size. ... it didn't dawn on me until later there is one thing I don't follow in the Silverfrost warnings -- perhaps that was your point of confusion as well and I misinterpreted the question raised. ... The location of the first member of those arrays might be of interest to look at--if there were anything suspicious in the Silverfrost implementation that's where it would seem to be. ...
    (comp.lang.fortran)