Jesse
Jesse
Okay, so I should update the Code::Blocks project with it disabled?? I'll see what other warnings I can access.
Alright then, that makes a lot more sense, it is rather annoying have five gazillion warnings spat out by the compiler. Also, I'm thinking of moving constructors to the source...
This is in place of `vfile` yes? So instead of having a buffer that we seek and read data from (similar to how an actual `FILE` works), we just have...
Okay, I think I see now. It's basically a better way to abstract the resource type and also saves a heap of code reuse (such as having heaps of calls...
Excellent, this sounds like this could work really well. Hopefully you can find a workaround for some of the weird formats (i.e models). You should be able to see what...
Looks good to me as long as this works. Might need to debug this a bit further if it's still causing issues/failures.
The amd64 bug is caused by memory pointer issues due to the 64-bit address space. IIRC it's trying to write to an incorrect space because the hardware only can support...
> Is ptr64 only used on x64? If so, why is it needed in comparison to just a `void*` or `FlatPtr` Currently, yes, however one could conceivably use this on...
> > FlatPtr is typdef'd to void* for the platform it's becoming compiled to right > > FlatPtr is essentially `ptrdiff_t`. It's an integer. I wonder if VirtualAddress or PhysicalAddress...
> I don't have strong opinion, but `Ptr32` / `Ptr64` feels like an overly generic solution to a very specific and unique problem. > > At a cursory glance, all...