i use std strings but when i import the string library the file become 1 mb

Is file size your main concern?

but why should i use a string for bytes

Ah, you need bytes, not characters? Well, use std::vector<std::byte> or std::vector<unsigned char>. Char is typically 1 byte size.

Ah, you need bytes, not characters? Well, use std::vector<std::byte> or std::vector<unsigned char>. Char is typically 1 byte size.

I'm getting this warning 'type cast': conversion from 'int' to 'void *' of greater size I don't understand what this means.

int countSubsets(vector<int> a, int sum) How can I pass another default integer variable n, but set it's value to a.size()?

It means the pointer size and int is different

For example, 64 bit ABI use 64 bit pointer, *nix use lp64 while windows use llp64. int is both 32 bit but pointers are 64 bit

Why don't you set it to -1 and change it to a.size() if it's still -1

It doesn't matter if the ram is below 4 GB, 32 bit still can hold it. It if greater than that, it will overlow

So I have converted a 32bit int to a 64bit because I casted it to a void pointer that is 64 bit?

No, the pointer size is 64 bit but you cast it into 32 bit

Ahh ok, I understand.

Use uint64_t or size_t to cast it. Best practice is size_t as different system can use different data model

So, (void*)((size_t)(374747+0x1F)) ?

Use uint64_t or size_t to cast it. Best practice is size_t as different system can use different data model

Casting from pointer to integer and vice versa should use uintptr_t or intptr_t. Not size_t. Because the pointer size can be bigger than the size_t. For example: C compilers on x86 real mode can have 32 bit FAR or HUGE pointers but size_t is still 16 bits.

Casting from pointer to integer and vice versa should use uintptr_t or intptr_t. Not size_t. Because the pointer size can be bigger than the size_t. For example: C compilers on x86 real mode can have 32 bit FAR or HUGE pointers but size_t is still 16 bits.

i tried this but if i use it on file -> read ( ret, size ); it says cannot convert

std::unique_ptr < char > ret ( new char [ size + 1 ] () );

i tried this now but it still not work auto ret = std::make_unique < char [] > ( size );

it tells me cannot convert unique_ptr < char [] > to char *

You can't store a pointer to char array as pointer to char, because it would be deleted incorrectly. You need to use std::unique_ptr<char[]>. Also consider std::vector, which can solve the same tasks, but will provide more useful functionality. As someone mentioned on stackoverflow, the only time you need unique_ptr of C-array is when you don't have std::vector available for some reason.

/warntime 12w

/warnlimit 3

you can create a fork process with fork() this will create a child process then you need to call your function by the child the fork() function returns a process id (if I’m not mistaken) the child process will work in parallel with your parent process (your main program) then in your main function you can use kill() with the process id to kill the child you’ve created

but then there are two processes running? i need one.

you can’t do this with threads using a child process is better because you can ask the OS to stop anytime

You may need to look at cross-platform frameworks like Boost or Qt.

yeah boost and Qt can do that too if you were doing it in C++ I thought you were coding in C but this is also how to do it natively in C++ too using kernel libraries choose whatever you like but the concept is the same 1- you create a fork (child process) 2- the fork calls your function 3- whenever you want your main function can ask the OS to kill the fork you can do this with threads but you will lose your sanity dealing with race conditions and undefined behavior in addition to mutex locks that will slow your program A LOT!!!

generally locks slows your program

Why do you think process is faster than threads? It's almost the same things

it is not, but locks that prevent race condition slow programs with multiprocessing it is easier to kill a child whether with another fork or its parent meanwhile controlling other threads is as simple as controlling a process

If you have a race condition you must to handle it in process as well as in threads. But process synchronization in more complicated

Yes, you should pay much attention to be able stop thread in legal way

No matching function for call to Player::Player() Friends, what is this error about, I can't understand?!

I get this error in the constructor implementation of another class where I used Player class objects

i believe its because your Player constructor expects some arguments and you are trying to instantiate it with no arguments