fuzztester

three pounds of stacks!

I just had a thought. I wonder if the idea of dynamically linked libraries in Unix and later of DLLs in Windows came somehow from the concept of overlays. And whether the overlay concept preceded (MS)-DOS.

Thanks, will check it out.

>He said some of his programs took a week to run on that beast (i.e. beast for that period) and then spat out one or just a few numbers as the result. :)

Running some kind of simulation or solving some hairy equations, probably.

Which books?

Turbo Pascal 3.x had it.

Question your premises.

1. What is the need to keep up with all of them (sheer volume - your own words)?

2. If you haven't kept up with them (as in, investigated them), how do you know they are cool and noteworthy. Just based on what others say?

Are the first use of 'scanner' and the second use of 'scanner' the same variable, or are they in different scopes. If they are in different scopes , would it be better to use a different variable, for the code to be more readable?

A good foo programmer can write foo in any language.

I am the creator of fortran-j, in which god is imaginary.

Probably means i for index.

I once visited the office of a scientist at the National Chemical Laboratory in Pune, India, where they had an Unix SMP RISC (2 MIPS CPUs) computer, IIRC, supplied by the company where I worked. He said some of his programs took a week to run on that beast (i.e. beast for that period) and then spat out one or just a few numbers as the result. :) I think the programs were in Fortran or C. That fairly expensive computer was used by only him. I was a bit in awe of that. It was a central government laboratory, huge campus, only one of its kind in the country, so I guess they had a good amount of funding.

Sometimes I think I should have gone into scientific computing. It seems pretty interesting.

Yes, if it is still extant by then, and not extinct.

But it likely will still be extant, along with COBOL. And Lisp.

I read somewhere that it was one of the first high level languages. There probably were a few others, which are less well known.

I had Fortran in college as one course. But we didn't have access to any computers to run our programs, because this was in India a few decades ago, in the just post-mainframe age, so we had to write all our programs on paper and submit them to the teacher for evaluation and scoring, ha ha.

>Inelegant code will still run reasonably fast

What do you mean by inelegant code in this context?

Non-idiomatic? Like non-Pythonic in the case of Python?

You guys haven't lived (and nearly died) until you've tried indian lasoon chutney, aka garlic chutney (with chilli), accompanied by aloo paratha or other paratha.

Yes, that way around, because it's the star of the show, not the paratha.

a time bomb.

niiice ... $?

To be enlightened, bhikkus append the suffix

  >/dev/null 

to the end of any command, thereby ensuring that they descend into nothingness.

alias nirvana=nothingness

ISOs of what, music or video?

You have to write them first.

Now trying to think of a Unix joke involving write, read and tee that also makes sense for the backup topic ...

ha!

I'll be glad to see a better Claude than Claude.

Thanks.

>It depends on what you mean by 'anything doable'. Eg Haskell compilers can in principle do lots of crazy optimisations that a C compiler would not be able to safely do, just because they don't have enough information. Even more so for Lean compilers, which can _know_ which of your loops are terminating, instead of making crude assumptions like C compilers.

Interesting. What are some of those optimisations that Haskell and Lean can do, that a C compiler would not be able to safely do?

>In CPython they are written in C (at the moment). Other Python implementations are written in other languages.

True. E.g.:

1. PyPy:

https://en.wikipedia.org/wiki/PyPy

>The PyPy interpreter itself is written in a restricted subset of Python called RPython (Restricted Python).

2. Jython:

https://en.wikipedia.org/wiki/Jython

>Implementation language: Python, Java

The article says the last release of Jython was 2 years ago. I wonder how much it is used these days. It did seem like a good idea when it was first released. I had only tried it out a little at that time.

Yep.

https://news.ycombinator.com/item?id=49913084

If hash tables were impossible to make in C, then it would be impossible to make them in Python, because it is a higher level language than C.

(Almost by definition, anything doable in a higher level language is doable in a lower level language, but not necessarily vice versa. In fact, many higher level languages are themselves written in lower level languages, e.g. Python is written in C.)

But Python has got dicts built into it, which are nothing but hash tables, and they are almost certainly written in C.

Google for some videos by Raymond Hettinger about Python dictionaries.

Or look at the source code of the Python interpreter.

IIRC, the first edition of the book "The C Programming Language" (aka K&R), by Kernighan and Ritchie, had a simple example of how to create a hash table in C, including with buckets to handle collisions. It was a simple algorithm. It simply added up the ASCII values of all the characters in the key, modulo some number.

Dr. Raja Parasuraman

some dumbkopf hners can't even handle historical stories and simple straightforward comments on them, so they downvote.

and yet they aspire to run or work in startups. ... hee hee.