isnt it short for "memory allocate"
It is
klimi
coal
then under what context would it not allocate memory
klimi
When there is no more memory to allocate
coal
w e l l
coal
that makes sense lol
coal
thats the size of the pointer
klimi
The return type of malloc is just a pointer... If you cast it into char pointer, it is still a pointer... There is no information about the size itself
coal
do sizeof(ptr)/sizeof(ptr[0])
coal
coal
but the return is also implementation defined
coal
for example, if you try to allocate a size 0, it can return null, or sometimes even a non-null pointer
coal
The return type of malloc is just a pointer... If you cast it into char pointer, it is still a pointer... There is no information about the size itself
there is no information about the size itself, yeah, its theoretically a stack
klimi
Heap is not a stack
coal
i mean its a stack in the sense that summing 1 to the pointer would return you the element after the current address
klimi
You mean that's "its a memory"?
coal
like, ptr[1] is literally short for "sum 1 to the pointer"
klimi
Its syntax sugar and it has nothing to do with stack or heap
klimi
You can do pointer arithmetics even in the static section
coal
You mean that's "its a memory"?
i mean that a pointer is only as big as its memory allocated, and whenever there is space there can be elements after the pointer's address
coal
Its syntax sugar and it has nothing to do with stack or heap
its syntax sugar yes, also [] operator is order-agnostic
coal
you can as well do 0[ptr]
klimi
i mean that a pointer is only as big as its memory allocated, and whenever there is space there can be elements after the pointer's address
No... Pointer does not have size... Its just a pointer... An address to virtual memory
coal
its a sum, you're just working on top of the memory layout in a pointer
coal
klimi
i mean that a pointer is only as big as its memory allocated, and whenever there is space there can be elements after the pointer's address
You have said that Pinter is as big
klimi
Pointer can point anywhere
coal
pointer can point anywhere then what does malloc do
klimi
Its just a number
coal
it indeed is a number thank you
coal
im talking about the memory layout that you interact with when dealing with pointers
coal
a pointer points to a memory address and thats it
klimi
pointer can point anywhere then what does malloc do
Malloc tries to allocate memory on the heap, if it is successful, it returns the pointer to the start address
coal
ill reformulate my statement
ɛ n h ᴀ n c ɛ ґ 🧟♂️
coal
a pointer itself has no size, but it covers only as much as the memory allocated for such
coal
a pointer itself has no size, but it covers only as much as the memory allocated for such
that is what i meant when i said its "big"
klimi
a pointer itself has no size, but it covers only as much as the memory allocated for such
What do you mean that it covers memory?
klimi
You can have 2 arrays next to each other and you can use the first pointer to point to the second array
klimi
Pointer covers all the virtual memory
ɛ n h ᴀ n c ɛ ґ 🧟♂️
Malloc tries to allocate memory on the heap, if it is successful, it returns the pointer to the start address
Can a function be created to allocate memory?
I mean a function which is user defined
coal
coal
what was the original topic again
klimi
Can a function be created to allocate memory?
I mean a function which is user defined
As long as it calls the syscall, sure
klimi
what was the original topic again
That pointer covers some memory, and I still dont understand what you mean by that
coal
That pointer covers some memory, and I still dont understand what you mean by that
no that was the debate we started after my misconception
coal
i understand what you said and you're right, i had a wrong idea of pointers regarding to their "scope"
coal
i joined this group especially to learn and help if i can
coal
so thank you as well
klimi
Oh no problem, I am here to discuss various topics. There is always things to learn
coal
agreed
Dastan
What is difference between do while and while
Dastan
?
coal
while executes after checking it
coal
as a matter of fact, do while will always run at least once:
do {
std::cout << "This is printed"
} while (0);
while (0) {
std::cout << "This wont be printed";
}
coal
it is also useful when you're receiving input, as the variables in the loop context are also accesible from the condition:
std::string input;
do {
std::cin >> input;
} while (input);
\Device\NUL
it is also useful when you're receiving input, as the variables in the loop context are also accesible from the condition:
std::string input;
do {
std::cin >> input;
} while (input);
You can also do that with this
int input;
while (std::cin >> input) {
if (!input)
break;
}
https://isocpp.org/wiki/faq/input-output#stream-input-failure
coal
You can also do that with this
int input;
while (std::cin >> input) {
if (!input)
break;
}
https://isocpp.org/wiki/faq/input-output#stream-input-failure
yeah, but in my opinion the input as a condition of the while feels more natural
coal
both are good approaches though
Suka
You can also do that with this
int input;
while (std::cin >> input) {
if (!input)
break;
}
https://isocpp.org/wiki/faq/input-output#stream-input-failure
while(std::cin>>input, !input){
do some stuff
}
perhaps? hehe
\Device\NUL
while(std::cin>>input, !input){
do some stuff
}
perhaps? hehe
Did you mean while(std::cin>>input && !input) ?
Suka
Did you mean while(std::cin>>input && !input) ?
yups but i guess we can use , as separator?
cmiiw
coal
#include <iostream>
int main() {
int input;
while (std::cin >> input, input) {
std::cout << "Received input: " << input;
}
return 0;
}
coal
try compiling this
A R A B I A N
Uh..Hello guys
A R A B I A N
Please I need a good YouTube tutorial for C++🙏🙏
coal
/get cppbookguide
Suka
its old school stuff hehe
Azhar
you need to know the beginning of the array and the size
void* getLastItemOfArray(void** Array, size_t Size) {
return Array[Size - 1];
}
iff you have a local static array you can use the sizeof trick, however this does not work for dynamically sized arrays or arrays passed as parameter to other functions.
But i can access by base address imean pointer
olli
But i can access by base address imean pointer
you can't access the last element of an array by only knowing the array's starting address.