yassim
Joined 15 years ago
Joined 15 years ago
Now you can wrap them up in C++, but then making such things hidden I think defeats some of their usage.
A managed runtime should be handle this better, but I don't know of any Java or .NET runtime that is optimised for a small memory foot print, perhaps paging from a larger virtual space[1]. I'd be interested to hear of any really.
[1] I do know there have been versions of Smalltalk that did basically this, but nothing recently that I've heard of.
I'm curious as to the problem you're exploring/solving here?
"Concatenated struct's in single chunk" is a neat trick. The use case seems a bit broken[1], but I'm assuming that it's from the original video, and your c++-ifying it? Or at least trying to find a nicer way to write this style of code?
If you'r going this route, I'd be tempted not to use pointers at all, and just use offsets and accessors.[2]
* Lack of pointers means you can load in 1 read. (endian needs to be watched, and assumes you can get the entire size elsewhere)
* You can also shuffle it around in memory should you be doing something fancy. (defragging heaps might be useful if doing a sandbox)
* Better encapsulation? maybe..
But the basic point I'd like to make is, there is no nice way to write this type of code, because c and c++ gives us no nice[3] way of expressing it.[1] Verts and Indices are generally uploaded to a GPU then discarded, but this has the counts, which is needed CPU side for draw calls, in the same chunk so would need to be copied before freeing.
[2]
struct Mesh
{
int32_t num_indices,
num_verts;
// inline to this struct..
// assumes Vector3 is aligned 4 bytes.
// and that Mesh has been alloced to same alignment.
//
// Vector3 positions[num_verts];
// int32_t indices[num_indices];
// Vector2 uvs[num_verts];
inline const Vector3* PositionsBegin() const { return reinterpret_cast<const Vector3*>(this + 1); }
inline const Vector3* PositionsEnd() const { return PositionsBegin() + num_verts; }
inline const int32_t* IndicesBegin() const { return reinterpret_cast<const int32_t*>(PositionsEnd()); }
inline const int32_t* IndicesEnd() const { return IndicesBegin() + num_indices; }
// etc
};
[3] Maintainable, fast at runtime, low mental friction to people other than the author, etcI do like the White box idea. I wonder though at the price where they start and if thats going to eat the profit generated. (I don't know, they could be very cheap to produce at scale.)
Sure could/should/must not be used to advertise the tech, but If I had a pocket watson, I'd have no problems with it calling it like it parses it.
>9. Latest research proves that Flame is indeed linked to Stuxnet....
Whats the chance that this "Resource 207" is some 3rd party module that more than 1 developer had access to? I concede that placing the same resource in the same resource location in 2 different unrelated applications is a bit of a long shot, but I dont see it as a smoking gun either.
1) Joker pushed another Joker or Cooperator. Which might be uncomfortable for a time, but would pass.
2) Joker pushed a Defectors, in which case some Defectors would want some form justice.
I have no numbers to prove this, just my feeling for the archetypes.
Allotments are chunks of land set aside for housholds to grow their own fruit and veg. Its generally an older gen (plus some younger woke) that use them, so nobody who the telegraph readers will care about. The councils have had a very hard time of it from the party in power due to many factors, and some are on the verge of bankruptcy. [1]
So being able to sell land that is genrally in walking distance to other residental zones to devlopers would be a welcome shot of cash. With the thin justification of "Its better for the enviroment" to keep most the would be defenders busy arguing if it is, or isnt, untill the deals are done, and they are lost.
It almost funny when the UK also has a general, saying that "Britain must train citizen army" [2], and allotments were promoted so the UK could feed itself when being blockaded. [3]
[1] https://www.theguardian.com/society/2023/dec/06/english-town... [2] https://www.bbc.co.uk/news/uk-68086188 [3] https://www.telegraph.co.uk/news/earth/environment/9996180/H...