Hi piple

Need to write lists

It includes add del search list

CLion

CLion is shit

vc2019 is slowly, how to tune it to make it as fast as vc2008?

Hello

How are you

Cool...n u??

can anyone review this code? and can it be optimized more? https://pastebin.com/t4tBMP1A

@TinkuBanna can u look into it

Yes but I don't know

Ok

1. Don't use the C header files (ending in .h ) in C++. Use the C++ version of those. 2. You're including headers you don't even need. 3. Lines 23 and 24 are exactly why do while exists. 4. using namespace std; 5. Line 39, 40 and 64 are why for exists. 6. Why are you passing NULL to strtok on line 37? 7. The if's could be replaced with a switch

I thought switch can only take char and int wasn't knowing that it can take strings😅 and passing null to terminate while loop 🙄 thanks for giving your time will try to improve 😁

1. Don't use the C header files (ending in .h ) in C++. Use the C++ version of those. 2. You're including headers you don't even need. 3. Lines 23 and 24 are exactly why do while exists. 4. using namespace std; 5. Line 39, 40 and 64 are why for exists. 6. Why are you passing NULL to strtok on line 37? 7. The if's could be replaced with a switch

@BinaryByter @mmihov sry for being intense... Can u help??

>2. You're including headers you don't even need. Wait, aren't you the guy who thinks that compilers are spotless at optimizing?=

ask us what you dont understand, instead of telling us that you don't understand it

Yeah i just told that... Its clear from my question/image that how does scanf works in this case...

And it won't increase runtime, but would increase compile time

1. Don't use the C header files (ending in .h ) in C++. Use the C++ version of those. 2. You're including headers you don't even need. 3. Lines 23 and 24 are exactly why do while exists. 4. using namespace std; 5. Line 39, 40 and 64 are why for exists. 6. Why are you passing NULL to strtok on line 37? 7. The if's could be replaced with a switch

ask EXACTLY what you don't understand

1) Don't use compile time arrays, they will fill your heap space up. 2) don't read a full line at once, because it will make you do the parsing twice 3) You can do the parsing recursively because you know that if there is something after the second operand, you have a second equation. do something like this: a + b if after b, you have another operation, you evaluate a + (b + c) for example that way, you don't even have to store the numbers, meaning that you will be less likely to fuck up and you won't even have to use the std::vecto

Whoa... Ya...how the output is coming in these cases...

reading...😅

what about using namespace std?

you probably understand the first one, right?

1) Don't use compile time arrays, they will fill your heap space up. 2) don't read a full line at once, because it will make you do the parsing twice 3) You can do the parsing recursively because you know that if there is something after the second operand, you have a second equation. do something like this: a + b if after b, you have another operation, you evaluate a + (b + c) for example that way, you don't even have to store the numbers, meaning that you will be less likely to fuck up and you won't even have to use the std::vecto

Ya..after that none...

shall i use dynamic array?