Re: Advice Needed...

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Stefan Berglund <sorry.no.koolaid@xxxxxx> wrote:
On Tue, 22 May 2007 09:24:14 +1000, "Michael C" <nospam@xxxxxxxxxx>
wrote:
in <u7Aeb8$mHHA.2596@xxxxxxxxxxxxxxxxxxxx>

Have a read of this one, it looks like they tried to have non-zero based
arrays but decided against it for very good reason.
http://www.panopticoncentral.net/archive/2004/03/17/290.aspx

An array of days of the month comes to mind right off hand. Why number it
0 to 30 when it could be 1 to 31?

Anyone who buys into that argument probably should give up a career in
programming. Every compiler is capable of compiling the offset as a
constant into the base address as - guess what - a ~constant offset~.

So if the .NET whoopdydoo can't account for an array offset which is a
compile time constant - not a runtime thing - then the wonder boys did a
crappy job designing that interface.

That's a "no duh!" from this corner, too.

Whoever wrote that article is blowing smoke - pure smoke.

Lessee... panopticoncentral, eh? Yeah, he does that for a living. He's the same
guy who decided to change the width of Integer and Long because -- yes, he told me
this -- because C programmers coming to VB couldn't be bothered to RTFM and were
constantly confused by the fundamental datatypes.

So, to be as clear as possible -- Paul Vick is the single person most responsible
for the destruction of the language. I'd call him a "lying dirtbag" but I'm sure
the accuracy of such a characterization (from either direction) is challengable.
Let's just leave this by pointing out that he holds the patent (on MSFT's behalf)
for iSnot.

Blowin' smoke - the microsoft way. They're still spreading the FUD and
covering their a$$es. Ludicrous this is.

That's Paul Vick's job, alright!
--
..NET: It's About Trust!
http://vfred.mvps.org


.

Relevant Pages

  • Re: OO programming - illumination? - whoopsie
    ... > represented by a host of loosely related arrays. ... > compiler and the memory allocators. ... A pointer is usually a word. ... organs can be further modeled to include cells and so on and so forth. ...
    (comp.lang.java.programmer)
  • Re: OO programming - illumination? - whoopsie
    ... represented by a host of loosely related arrays. ... compiler and the memory allocators. ... As a matter of fact there is no such thing as a pointer. ... memory that just holds a terminator, which is 0 by convention. ...
    (comp.lang.java.programmer)
  • Re: COBOL tool
    ... has a virtual length of 9 digits but occupies 5 actual bytes), ... it is called a 'compiler'. ... How hard would it be to write a couple of lines around a record layout ... and have a popup window that would give you the offset ...
    (comp.lang.cobol)
  • Re: Criticisms?
    ... justified today with machines 10 000 or more faster than a PDP-11. ... the feature were "built-in" to the language. ... but lean enough that the compiler can still do a good job. ... The interchangeability of arrays and pointers is pure genius (it maps very ...
    (comp.lang.c)
  • Re: Double precision arrays and subroutines
    ... arrays. ... What happens is that, in Fortran, these two program units are ... The subroutine and the program that calls it are compiled ... and normally the compiler doesn't know about one when it's ...
    (comp.lang.fortran)