366 % 7 always produce reminder 2

If(year % 100 == 0) { If(year % 400 == 0) //Year is leap } If( year % 4 == 0 ) // Year is leap Else //Not leap

If it divides by 400 it divides by 100

if the year number is divisble by 400 or by 4 but not 100 it is a leap year

It can't be divisible by 400 and not by 100 tho

What's the point of the 100 division?

of course not. but if it is divisible by 100 but not by 400 is no leap year

If(year % 100 == 0) { If(year % 400 == 0) //Year is leap } If( year % 4 == 0 ) // Year is leap Else //Not leap

just if(yr%4)return 0; if(!yr%400)return 1; if(yr%100)return 1; return 0;

just if(yr%4)return 0; if(!yr%400)return 1; if(yr%100)return 1; return 0;

if (year % 4 == 0)return true;

if (year % 4 == 0)return true;

returns true on 1900 which is not a leap year

just if(yr%4)return 0; if(!yr%400)return 1; if(yr%100)return 1; return 0;

It returns 1 for 2000 since !2000%400=1

returns true on 1900 which is not a leap year

just if(yr%4)return 0; if(!yr%400)return 1; if(yr%100)return 1; return 0;

yes but the same for 1900 2000 is a leap year, 1900 is not. so the result should differ

returns true on 1900 which is not a leap year

How would your extra 100 and 400 divisions help with that?

bool isLeapYear(int year) { if (year % 400 == 0) return true: if (year % 100 == 0) return false; if (year % 4 == 0) return true: return false; } — or— bool isLeapYear(int y) { return y % 100 == 0 ? y % 400 == 0 : y % 4 == 0; }

bool isLeapYear(int year) { if (year % 400 == 0) return true: if (year % 100 == 0) return false; if (year % 4 == 0) return true: return false; } — or— bool isLeapYear(int y) { return y % 100 == 0 ? y % 400 == 0 : y % 4 == 0; }

bool isLeapYear(int year) { if (year % 400 == 0) return true: if (year % 100 == 0) return false; if (year % 4 == 0) return true: return false; } — or— bool isLeapYear(int y) { return y % 100 == 0 ? y % 400 == 0 : y % 4 == 0; }

If(year % 100 == 0) { If(year % 400 == 0) //Year is leap } If( year % 4 == 0 ) // Year is leap Else //Not leap

Got confused, because the 100 was before the 400 here

If we divide year first by 100 and if it is divided by 100 we divide it by 400 otherwise divide by 4

@ollie I have a short question

i=7, j=8, k=9; printf("%d", i-7 && j++ <k); printf("%d %d %d", i, j, k);

@ollirz btw

If there was ||, not &&; would right side be evaluated?

yes exactly, the expression on the right side will be evaluated if the left side is false, which holds for this case Using ||, if the left side is true however, the right side will not be evaluate because true or anything is always true To cite the standard [expr.log.or] The || operator groups left-to-right. The operands are both contextually converted to bool. The result is true if either of its operands is true, and false otherwise. Unlike |, || guarantees left-to-right evaluation; moreover, the second operand is not evaluated if the first operand evaluates to true. The result is a bool. If the second expression is evaluated, every value computation and side effect associated with the first expression is sequenced before every value computation and side effect associated with the second expression.

Thank you so much !

Structs are just legacies from C

In c++ a struct is a class with default accessibility set to public @Kurimi

in structs by default members are public

do you know why structs are by default public? they have to align with pod from c

That is not true as struct in C++ can hold a virtual table if you declare virtual functions inside

this is just some late additions, c structs can never do that

this is just some late additions, c structs can never do that

Also, nothing prevent you from including function pointers in a C struct

Making it effectively a vtable

Also, composition tricks C into having inheritance in structs

that's gnu extension far as i know

No, just putting a field at the beginning for your struct declaration that is the generalization