Justas Masiulis

List of things that should get into the object class - [x] NtDuplicateObject (no ability to select source process) - [x] NtMakeTemporaryObject - [x] NtMakePermanentObject - [ ] NtSignalAndWaitForSingleObject -...

Currently `OBJECT_NAME_INFORMATION` structure has a single `UNICODE_STRING` member. It would probably be the best to move the query for this straight into the `basic_object` structure and create a wrapper type...

at the moment only ntw::system namespace and ntw::memory components are tested. It would be great to have a test suite that covers most of the library.

Should set up appveyor

It would be nice if we could add allocator support. They are pain in the ass to add and probably not that useful. Thoughts?

probably in need to remove constexpr specifiers if building on VS2015

need to integrate wow64pp to allow querying of whole 64 bit memory range

Don't have VS2015 installed so cannot debug to find out the issue. It probably is related to wrong constructor being used

Contextual alternative for 'x' causes visual inconsistency in hexadecimal numbers

1

Many languages use `0x` prefix to express hexadecimal numbers; because both a letter and a number can follow after, it causes a bit of inconsistency. [small example of this behaviour...