paxcut

Found what i was looking for. with this changes ```cpp struct FileUint { if (header.pointer_size == HeaderPtrSize::_32) u32 old_ptr_base; else if (header.pointer_size == HeaderPtrSize::_64) u64 old_ptr_base; else std::sys::assert(true,"Invalid data size");...

I can't comment on that assessment. I am just trying to show a way to achieve the results the feature you requested would show with the existing code. Adding new...

If you expect `temp::unknown` for -1 then you should also expect `temp::fe` for -2 based on definition ```cpp enum temp : s8 { unknown = -1, fe = 0xfe, //0xf2...

i uncommented top one only and i dont get any errors. it is true that the format function is not used in that case because using @ inside a struct...

you are right. my input file got overwitten somehow which turned wrong result. still you should not use @ inside structcts and use $ instead.

I revised the code to use $ to avoid effect of creating views ```cpp #include "std/string.pat" fn entryName(auto e) { return e.name; }; struct Entry { u32 nameOffset; u32 nameSize;...

After ir reads the name "test" the 1234 gets assigned to the nameoffset and the namesize becomes a huge number that overflows.

the problem was with going back and forth because the strings occur before the data needed to read them. Notice that only the first string offset is needed because the...

You are right about auto offset not needed, nice catch! I totally missed that. To answer the issues of maintainability and keeping the data in one place here is code...

I edited the previous post to something a bit more helpful or at least i hope it is.