I had blanked this from my memory, but my very first programming job was to reimplement some FoxPro code in... Visual Basic. FoxPro is so strange to work in. It's like programming in SQL, and the codebase I was in had global variables everywhere.
xthexder
I don't use 256 bytes everywhere. I use a mix of 64, 128, and 256 byte strings depending on the specific use case.
In a hot path, having the data inline is much more important than saving a few hundred bytes. Cache efficiency plus eliminating heap allocations has huge performance benefits in a game engine that's running frames as fast as possible.
22 characters is significantly less useful than 255 characters. I use this for resource name keys, asset file paths, and a few other scenarios. The max size is configurable, so I know that nothing I am going to store is ever going to require heap allocations (really bad to be doing every frame in a game engine).
I developed this specifically after benchmarking a simpler version and noticed a significant amount of time being spent in strlen(), and it had real benefits in my case.
Admittedly just storing a struct with a static buffer and separate size would have worked pretty much the same and eliminated the 255 char limitation, but it was fun to build.
One cool trick that can be used with circular buffers is to use memory mapping to map the same block of memory to 2 consecutive virtual address blocks. That way you can read the entire contents of the buffer as if it was just a regular linear buffer with an offset.
I came up with a kind of clever data type for storing short strings in a fixed size struct so they can be stored on the stack or inline without any allocations.
It's always null-terminated so it can be passed directly as a C-style string, but it also stores the string length without using any additional data (Getting the length would normally have to iterate to find the end).
The trick is to store the number of unused bytes in the last character of the buffer. When the string is full, there are 0 unused bytes and the size byte overlaps the null terminator.
(Only works for strings < 256 chars excluding null byte)
Implementation in C++ here: https://github.com/frustra/strayphotons/blob/master/src/common/common/InlineString.hh
It's not actually the transistors that break down in flash memory. Flash memory works by storing charges in what is effectively a grid of capacitors, and in order for the data to remain stored, the insulating oxide layers in the cells need to be preserved. Every time a cell gets written, a charge is forced through the insulation with high voltage, and this degrades the insulation. A single flash cell might only have a few 1000 writes before this insulation goes bad and it no longer holds data. Modern SSDs have wear levelling techniques to make the drive as a whole last longer.
Transistors on the other hand don't have any inherent degradation that I'm aware of other than external factors like corrosion. The first thing that's likely to die on a GPU is the electrolytic capacitors in the power filtering electronics, which have fluid in them that dries out over many years.
Elaborate?
This guy should be smart enough to realize he's complaining about not getting free storage from Google. You can't just run a business off other people's infrastructure and expect it to work out without any business agreement or contract. Google Workplace is a thing, and it sounds like this guy is just cheap if he won't pay for either it or his own harddrives.
I still have gmail polling my old hotmail//live addresses, and it's been that way since the day I signed up. Back when the slogan was still "Don't be evil"
I guess not every place does this, because I swear the last few times I've been on hold I got transferred 2 or 3 times and had to re-explain my entire issue all over again to each person.
It's always a treat to find a new Monty Python sketch. I hadn't seen this one either and had a good laugh
I've already been discussing this. Maybe read the rest of the thread.
I think you're missing the point of why. I built this to be a nearly drop in replacement for the standard string. If this wasn't the case it would need to do even more processing and work to pass the strings to anything.
Standards don't matter for an internal type that's not exposed to public APIs. I'm not trying to be exactly compatible with everything under the sun. There's no undefined behavior here so it's fine