Curl now uses the idiom where the linked list data (prev/next pointers) are inlined in the same struct that also holds the payload
And when you have a memory overwrite then your meta data is corrupted and you loose the complete list.
I keep my meta data and payload in two separate list for that very reason.
So you structure your code to get more subtle errors in case of memory overwrites? "Loosing the complete list" sounds catastrophic and like something that would be easily noticed , and thus fixed.
Arranging the code to "keep trucking" in case of spurious memory overwrites seems like setting it up to be hard to debug, and having programs run in some ill-defined state where some portion of data has been overwritten but nobody notices is just super-scary.
Looks like a good start.
I would love to get a full replacement of TotalCommander for macOS. I've tried a few and I'm currently using Forklift 3.
There's still some features that I'm missing in Forklift so I'll keep an eye on this project.
yes mucommander, it could open websites too. it literally parsed html and showed you list of included resources in the panel. how cool is that? :-) which commander has that?
Path Finder is pretty good. I'm still not sure I exactly love it though I should maybe take the time to customize it one of these days. You end up back in Apple's Finder in program dialog boxes in any case.
Way back when, I sold a shareware file manager for DOS. I think the program was something like 32KB. :-) Times have changed.
When I started to program in C I used "n" for the longest time, simple because it was quicker on to type on my first computer; "Next N" was a quick two taps on the N key.
Guess the platform :-)
Where I live (lived) there's no such thing as free local calls. Whenever you dialed anything the meter started counting.
I became very good at mentally preparing what I wanted to download before dialing :-)
That was pre-internet, at least where I lived, and we all used Fidonet[1]. Cant recall my node, it's been too long.
I was a bit late to the internet game (I think ~1997), but this was the same in the UK too. Most ISPs had expensive
subscriptions which gave you access to a freephone number. In 1998, AOL was £16.95 a month [0].
I can't remember who I started out with, but I switched to FreeServe after they launched. They provided subscription free access to a local rate number (which confusingly doesn't have to be geographically local), and made money by getting a cut of the call rates. I don't think they were the first to do this, but they had a partnership with one of the main computer retailers. They were so successful an investigation was launched by the regulator [1].
They provided subscription free access to a local rate number
And most [Well at that time really just BT or Cable/Wireless] telcos gave you free local calls. You just had to make sure you wasn't connected for more than an hour. I remember a program would disconnect and connect your modem every X minutes.
I remember back then [and to this day] my mind being blown that I was chatting to someone and there is a physical connection between us - there was a signal I was sending that had to use a physical wire connection all the way to their computer, so we could discuss topics we had only just discovered. Yes we felt special.
For me the 'magic' of the internet is now lost on people. It may not be a bad thing; I don't know, but it's accepted now we are always connected.
Back then, when you connected to the real internet [not AOL etc] it was like walking into the biggest library you had ever known and if you chose to be alone to take in that knowledge - you could. If you also wanted to engage with other people in the library - you would be polite and there was a mutual respect for you and your opinions. You could then leave the library and return when/if you wanted.
Rose tinted glasses maybe - but it's a very different Internet now.
The Danish plant is about an hours drive from me. There's not much IT related going on in that area so it's good to see that someone is willing to invest.
However I'll continue to use wireshark for debugging my network code when at the office.