And when we define variable, it has this data before initialization.

wouldn't you be better off asking to friends or people that you know irl and near your location

The ppl I know don't know anything about laptops. They just buy what's showing on stand in PC Richard and son

or buying online, there's amazon and ebay

try Facebook marketplace or something idk, this is likely the last group that would be of use

yes, then this unused memory is now of value, even if its not defined by your program yet

So why when we cout heap's free to use (m[6]) is empty, not previous value

Anyone help for making cards game

Thanks, now i understand

??

make the game yourself and when you encounter an issue you can ask for guidance

you're welcome

[10:40 AM] Harshit Shukla (Guest) std::array<col, 6>table; //create a table with 5 columns of col type introw_number=0; // std::string pid, name, gender, age, fare; std::stringrow[6]; while(!file.eof()){​​​​​​​​​ for(intcount=0;count<5;count++) {​​​​​​​​​ getline(file, row[count], ','); table.at(count)[row_number]=row[count]; }​​​​​​​​​ getline(file, row[5], '\n'); table.at(5)[row_number]=row[5]; row_number++; }​​​​​​​​​ DisplayColumn(table[1]); ​[10:41 AM] Harshit Shukla (Guest) voidDisplayColumn(std::array<std::string, 891>&col) {​​​​​​​​​ for( autovalue :col ){​​​​​​​​​ std::cout<<value<<"\n"; }​​​​​​​​​ }​​​​​​​​​ any help what is happening in this program

Cause the code is really long

Yeah, I use

np

Need to parse json content

use a state machine

what do you want to return, string values of the json?

Is there any way contents of a file can be cleared fully in c++

Is there any way contents of a file can be cleared fully in c++

#include <stdio.h> main(){ int i, x, total; total=1; printf("ENTER ODD NUMBER BETWEEN 500 and 1000"); scanf("%d",&x); if(x%2==0||x<500||x>1000){ printf("INVALID"); } else{ for (i=x;i>0;i--){ total=total*i; } printf("THE FACTORIAL IS %d",total); } }

#include <stdio.h> main(){ int i, x, total; total=1; printf("ENTER ODD NUMBER BETWEEN 500 and 1000"); scanf("%d",&x); if(x%2==0||x<500||x>1000){ printf("INVALID"); } else{ for (i=x;i>0;i--){ total=total*i; } printf("THE FACTORIAL IS %d",total); } }

#include <stdio.h> main(){ int i, x, total; total=1; printf("ENTER ODD NUMBER BETWEEN 500 and 1000"); scanf("%d",&x); if(x%2==0||x<500||x>1000){ printf("INVALID"); } else{ for (i=x;i>0;i--){ total=total*i; } printf("THE FACTORIAL IS %d",total); } }

6.112885498 E+1136 is factorial of 501, smallest number in your case. C can do (2^64) - 1 if you use unsigned long... which is not going to get you anywhere.

Different arch has different size in data type, consider using uint64_t

C++ is basically C with classes

Is there any way contents of a file can be cleared fully in c++

garbage is when you initialize a new pointer and dont delete it when you're done using it

Garbage varies from OS to OS on few there are hardened runtimes which zero memory where possible during allocation, free, and resource reclaim in order to prevent attacks that take advantage of left over memory that could hold secrets of some kind that they should not know about, say passwords left over in memory On most, memory will be left uninitialized as it is reused by programs, uninitialized memory may contain garbage This garbage data may have been useful data for a previous program that was running (P1 exits which causes 0x56 to be released back to the system, P2 allocates the free 0x56) This garbage data may have also been useful data for a running program that has since freed that memory (P1 frees 0x56, P2 allocates the free 0x56) Do note that most garbage is from malloc/new since they recycle freed memory globally by all programs In most cases when a program starts up it will be allocated memory for its main stack eg the main thread, usually a very generous 8 MB depending on OS and thread implementation normal threads will have a much smaller stack unless explicitly requested a larger stack upon thread creation, as they do not normally need to run a full program and manage lots of stack variables and stuff since all that is shared with the main thread via address space sharing (differs from OS to OS) this memory may or may not have been previously used by another program that has since freed that memory Eg on a freshly booted system it is likely the entire RAM is filled with zeros and most new programs will receive zeroed memory until recycling kicks in (assuming when RAM powers off its entire contents is effectively zeroed due to it not retaining any data) Tho the kernel may also unintentionally cause new programs to get garbage when fresh booted even if no programs have started yet and it is only the kernel init process running (the kernel itself (or sysd, can't remember) is usually init with pid 0, OS dependant tho) Also note that if a process or libc implementation zeros it's allocated memory address 0x56 before freeing it then another program allocating the same memory address will receive zeroed memory since 0x56 was zeroed before it was freed Tho this zeroing of memory should NOT be relied on and callers should use calloc to unsure zerod memory if memory will be partially overridden (calloc is usually much faster than malloc + memset) or malloc/new if all memory will be FULLY overwritten and not read before it is overwritten