Cube
JF BastienArray indices start at 0 in C, but start at 32 in F.
All the math geeks: “but what about R???”
Scott Michaud@jfbastien 459.67.
I'd make a joke about doing a for loop over floats, but I've been doing a lot of graphics dev lately...
Fabian Giesen@jfbastien ok fine, Array indices start at 0+0i in C and 0 in R
Petr Tesařík
_L4NyrlfL1I0@jfbastien Do they start at 273.15 in K?
@yrlf of course.
joe@jfbastien
don't be sharp
don't be sharp
orva@jfbastien I wonder if F# has proper imperial arrays available
Kroc Camen@jfbastien ASCII is Imperial*, makes sense 🤔
* Printable codes start from 32 / 0x20
Giles Goat@jfbastien .. that's why my Fortran code was never working...
Ashley Gay@jfbastien i measure my temperatures in radians fahrenheit :3
chfkch 
Dani (
Antifascista)
Erik L. Arneson 
@jfbastien Does this mean they start at about 10.67 in D?
LR
I Can't Believe It's Not Zero!@lritter @jfbastien are we Rankine languages based on array indexing choices?
AMS@jfbastien Must be a 5x9 array.
John Regehr@jfbastien it's efficient because it's a power of 2 🤔
@regehr spoken like a true ‘merican!
Pierre H.@jfbastien that’s why no one uses C# or F# which raise this by a semi tone
KarenTurley
Tokiko Studio@jfbastien
And then Lua 🥲
And then Lua 🥲
Jan Walzer@jfbastien
does that mean the arrays in R explode at [80] ?
does that mean the arrays in R explode at [80] ?
Till O'Rly 
@jfbastien
In D it's 10.6̅, then.
In D it's 10.6̅, then.
Lulu 🍉 לולו@jfbastien off by farenheit
John Sturgeon@jfbastien Makes about as much sense as arbitrarily assigning temperature scales to water freezing and boiling points.
Of course... that would also mean that if you're at 1,500m elevation your index would have to be a float since water boils at 95.06º C
Florian Gilcher
Patrick Wu 
@jfbastien and 273.15 in K, 1 in R
Fubaroque@jfbastien It’d make more sense to compare with JavaScript. Where arrays can be indexed by a real value instead of just an integer. 🤣
IPng Networks
Wolf_Baginski@jfbastien
So they have space for them?
So they have space for them?
beka valentine@jfbastien @cstross this sounds like something intercal would do
Charlie Stross@beka_valentine @jfbastien Nah, Perl 4 had the $[ operator to redefine the array base index. (I believe one of the later Perl 5 releases deprecated it and Raku just said "nope". Spoilsports!)
@cstross @jfbastien fuckin perl
dakkar@cstross 5.12 deprecated it, 5.30 made it mostly constant (
@beka_valentine @jfbastien
$[ = 1 is a runtime error now)@beka_valentine @jfbastien
Oriel Jutty 
@dakkar @cstross @beka_valentine @jfbastien
FMTYEWTK about the history of $[:
1987-12-18: perl 1.0 is released, featuring the
$[special global variable that lets you change the array base index whenever you want. (Mainly, I suspect, to make life easier fora2p, the awk-to-perl translator also included in the release, because array indices start at 1 in awk.)1994-10-17: perl 5.0 is released. It still supports
$[(anda2p), but the semantics of$[have changed: It is no longer a real variable; instead, assignment to$[is treated as a compiler directive that affects the current file only. Now module authors don't have to worry about someone else changing$[at runtime. The documentation describes its use as "discouraged".2000-03-22: perl 5.6.0 is released. No real change to
$[, but its documentation now calls it "highly discouraged".2007-12-18: perl 5.10.0 is released. The semantics of
$[are tightened further: Assignment to$[only affects the current lexical scope, not the whole file it is in, bringing it in line with other compiler pragmas (use strict,use warnings, etc).2010-04-12: perl 5.12.0 is released.
$[is formally deprecated (it was only "highly discouraged" before).a2pno longer generates code that sets$[.2012-05-20: perl 5.16.0 is released. The implementation of
$[has been pulled out of the perl core proper; it is now provided by thearybaseextension module. Also, any code that doesuse v5.16(to both require at least perl version 5.16 and opt into all the new features provided by perl 5.16) no longer has access to$[: Reading from it always returns 0; assigning a non-zero value to it is a compiler error.2015-06-01: perl 5.22.0 is released. It no longer includes
a2p, which has been moved to its own CPAN distribution (App::a2p).2019-05-22: perl 5.30.0 is released. 25 years after its use was "(highly) discouraged" and 9 years after its formal deprecation,
$[has been effectively removed. (Theuse v5.16semantics of$[are now always on: Assigning 0 to$[has no effect; assigning anything else is a compiler error.) Thearybasemodule no longer exists.
The Manchurian IdiotBill the Lizard (@[email protected])
"Should array indices start at 0 or 1? My compromise of 0.5 was rejected without, I thought, proper consideration." — Stan Kelly-Bootle
@jfbastien This is not accurate. Indices always start at 0, but in F array elements <32 are frozen.
Harald
Dario$ (@[email protected])
Allegato: 1 immagine #programming #meme #software #computerscience
KI7CFO@jfbastien ohhhhh programming joke that if you don't know programming you think it is about temperature.
Qole@jfbastien
That's cold, man.
That's cold, man.
Diogenes Van Sinope@jfbastien Everyone talks about off-by-one errors but nobody talks about the off-by-thirty-two errors.
And whatever happened to F++ ??