C uses ^ for bitwise xor and a function for exponentiation, though.
No, C does not have an exponentiation operator! Possibly you meant "and not a function for exponentiation". I should have said "followed Fortran rather than BASIC".
I meant exactly what I said. C uses a function for exponentiation. Nothing that uses ^ for powers follows C's lead.
No, C does not have an exponentiation operator! Possibly you meant "and not a function for exponentiation". I should have said "followed Fortran rather than BASIC".
I meant exactly what I said. C uses a function for exponentiation. Nothing that uses ^ for powers follows C's lead. https://en.cppreference.com/w/c/numeric/math/pow.html
Oh, I interpreted "a function for exponentiation" as being part of a list of things C uses ^ for. It didn't even occur to me that the sentence had an alternative parsing where it was part of a list of things C uses. C does indeed use a function for exponentiation. And time flies like an arrow!
Well, not as bad as something like public static function words(string $document): array { which some languages these days are coming up with.
While I agree, at least here every word, though is verbose, at least means something, whereas “HOW TO RETURN” carries no more meaning than “def”.
> public static function words(string $document): array {
>, though is verbose, at least means something
I disagree, it is hardly verbose. there can be further detailing of the input and return value of the function beyond a simple type. Java didn't go far enough, not by a long shot - we need hardcore painstaking, completely brutal typing. Such typing will be highly beneficial for software reliability - you're not against reliability are you?
> 2**1000 = 2^1000 The reason for using `**` is that `^` is widely used for bitwise exclusive-or. So commonly `2**1000 != 2^1000`!
I think Fortran used ** because EBCDIC didn't have ^ or uparrow. ABC and Python followed Fortran rather than C on this point. units(1) supports both.
BCD, actually, given that Fortran dates from the mid-1950s. EBCDIC only appeared more or less around Fortran IV, in the early 1960s. Many printers in those days had a 48-character chain/train. After upper-case letters, digits, and a few essential punctuation marks (like . and ,), you weren't left with many options. The 60-character set of PL/I was a luxury back then, let alone lower case.
There's even a book. I have it (and have had it for a loooong time). I tried to do some larger things with ABC back in the day. It was nice. Then Python arrived. I think I still have the muscle-memory for the editor.
I think Fortran used ** because EBCDIC didn't have ^ or uparrow. ABC and Python followed Fortran rather than C on this point. units(1) supports both.
BCD, actually, given that Fortran dates from the mid-1950s. EBCDIC only appeared more or less around Fortran IV, in the early 1960s. Many printers in those days had a 48-character chain/train. After upper-case letters, digits, and a few essential punctuation marks (like . and ,), you weren't left with many options. The 60-character set of PL/I was a luxury back then, let alone lower case.
I swear I remember using this. I even remember the syntax. I was able to compile it and just start writing in it. I have no idea how I know this syntax. Did early linux have this? Maybe netbsd? I actually found it. It was on simtel: https://archive.org/details/Simtel20_Sept92 I must have gotten it from there. I would routinely get any thing Walnut Creek would make. I also realized a couple years ago I could navigate…
Can you tell me about "Simtel"? I have never used a BBS but from looking at that ISO it was a collection of software downloaded from BBS' ?
FTP server, not BBS. You had to be on the Internet to access it.
It was called SIMTEL20 for a while because it was hosted on a PDP-10 mainframe running the TOPS-20 operating system, but apparently it was hosted on a PDP-10 running ITS first:
> The archive was hosted initially on the MIT-MC PDP-10 running the Incompatible Timesharing System,[1] then TOPS-20, then FreeBSD servers