"Freestanding"?

"Freestanding"?

Means no library

Means no library

Oh, thank you

Does that also exclude the standard library?

Does that also exclude the standard library?

http://eel.is/c++draft/compliance#:implementation,freestanding

Does that also exclude the standard library?

Yes, freestanding only include a tiny set of headers, it is implementation defined whenever exceptions exist, and is mostly used for kernel level development and embedded development

17

17

thx

/report screen photo and asking to solve test without trying it first

^o^

lol

y=(x!=11)?x++:x--; ?

y=(x!=11)?x++:x--; ?

What is the value of x here??

10

y=(x!=11)?x++:x--; ?

If x=10 then y will end up being 11, right?

y=(x!=11)?x++:x--; ?

is it more homework?

😂😂

yes

oof

y=(x!=11)?x++:x--; ?

I think the answer will be 10

its my 2 week in C++

don’t think please be sure because there is mark 😂

marks*

both x and y would become 11

Oh sorry y will be 10 and x will be 11

y=(x!=11)?x++:x--; ?

Bruh

y=(x!=11)?x++:x--; ?

y is 10 if x is 11, otherwise y is x plus 1, since x cannot be known as its value is not known completely, only that it COULD be a specific value, and if it is this specific value, then perform Z action on X assuming it is that specific value

y=(x!=11)? x++:x--; is the same as

x= 10 initially you need to determine the value assigned to y

If (x!=11) y=x++; else y=x--;

In both cases observe that y=x and a change occurs in x only

x= 10 initially you need to determine the value assigned to y

then y is 11

So a compiler might rewrite this as

y=x (x!=11)? x++:x--;

Sorry, x becomes 11 y becomes 10

So y=x is always true

And then a change occurs in x later on

No

#include <stdio.h> int main(void) { int x = 10; printf("%d", (x != 11) ? x++ : x--); printf("\n%d", x); }

#include <stdio.h> int main(void) { int x = 10; printf("%d", (x != 11) ? x++ : x--); printf("\n%d", x); }

Just use this code

And understand what happens

oh yea, its x++ and not ++x

Oh sorry y will be 10 and x will be 11

Ooohhhh true

so either way, y is 10 lmao

Nice breakdown

oh yea, its x++ and not ++x

This always gets me :[

there we go :) all nice and readable :)

print that out and glue it to your homework as the answer 😂😂😂😂😂

y=x (x!=11)? x++:x--;

@smallville7123

You're repeating code for no reason

You're repeating code for no reason

heh

You're repeating code for no reason

worth it

worth it

No

No compiler is going to compile it that way either

No compiler is going to compile it that way either

i know

y=(x!=11)? x++:x--; is the same as

but its the unoptimized translation of that :)

as the elvis operator is basically an if else shorthand condition ? doThisIfConditionIsTrue : doThisIfConditionIsFalse same as if (condition) { doThisIfConditionIstrue; } else { doThisIfConditionIsFalse; }

Can anyone solve this?

Can anyone solve this?

No

Do your homework yourself first

Do your homework yourself first

None of your business

None of your business

True, not my business anyways, suit yourself.

None of your business

After such shit attitude you expect help?

Anyway the solution is simple, use a std::unordered_table

And put values into it

Hey, is it logic if I want to make the user to decide the array size to do like that? int userSize int arr[SIZE] ; SIZE = userSize; ?

Hey, is it logic if I want to make the user to decide the array size to do like that? int userSize int arr[SIZE] ; SIZE = userSize; ?

Use malloc and create the array on heap if you want a variable sized array after getting input from user

Hey, is it logic if I want to make the user to decide the array size to do like that? int userSize int arr[SIZE] ; SIZE = userSize; ?

Possible but a very bad idea

Afaik the size of the array should be a const if you're declaring an array. But since const isn't enforced properly you never know

Afaik the size of the array should be a const if you're declaring an array. But since const isn't enforced properly you never know

VLAs are a thing

Afaik the size of the array should be a const if you're declaring an array. But since const isn't enforced properly you never know

you can use stack allocation technique

Use malloc and create the array on heap if you want a variable sized array after getting input from user

I don't think I got ther yet.. I'm in the task of learning array on c.. And they ask me to make the user to decide the size and then hell puts the numbers and then I need to check if the size number was in the array and how many times 🥺

VLAs are a thing

Ah yeah, you forget these if one uses C++ too much

Ah yeah, you forget these if one uses C++ too much

C++ is quite weird

C++ is quite weird

No u, you sire are weird XD

No u, you sire are weird XD

I've seen weird bs like scoped fds

I've seen weird bs like scoped fds

Welp, I can't even refute that 😔