not really

array semantics are beautiful/interesting/fascinating

std::cout << 1["ABC"];

little example I just found that illustrates my point quite welll

std::cout << 1["ABC"];

@HUNCHOASH whats the output of this?

Correct

Do you know why?

...

but "1" is not a string

its an int

but here we have it like this:

1["ABCD"]

yes

but why?

😉

Basically its because a[b] is evaluated to *(a + b)

and through commutativity *(1 + "ABCD") can be changed to *("ABCD" + 1)

which is equivalent to str[1]

Basically its because a[b] is evaluated to *(a + b)

correct

yes

first of all, MAXI is not a string

first of all, MAXI is not a string

I think it is an const int

not defined here

lol, the modification.

I think it is an const int

are u sure?

does compiler automatically unchanged variables makes const?

does compiler automatically unchanged variables makes const?

no

this has got to be one of the more awkward uses of operator« xDDD

this has got to be one of the more awkward uses of operator« xDDD

no

🤔

this has got to be one of the more awkward uses of operator« xDDD

this has got to be one of the most awkward uses of cxx (I am talking about webcpp)

this has got to be one of the most awkward uses of cxx (I am talking about webcpp)

xDDD

this has got to be one of the most awkward uses of cxx (I am talking about webcpp)

i have got the login working

just in 3 hours of work

if you'll show me working csrf protection in your webcpp form I'll like it

csrf?

yes

but what about....

If I need to edit the view so I'll need to recompile my code everytime?

slight downside to webcpp

btw: csrf security is planned on

(not yet implemented)

I wonder how that will work I implemented basics of csrf into my framework but I lost it when I was thinking about how to implement that on a client side

well basically you store a secret key in the cookies

and you alter that often enough

and you store that secret key in your db

and if the keys dont match, the cookies are forged

wait... why I didnt use cookies lol

oh I didnt have them implemented at that moment xD

maybe because your shit didnt support cookies?

it does now

oh I didnt have them implemented at that moment xD

WEBCpp is more advanced than your shit 😉

it does now

proof required

lol I don't even feel sorry

Ok wait

xDD

Lol jk

*hires bunch of indians to write that in 5 mins*

you are showing me a disgrace by doing that

yeah, so that literally will be shit.

exactly

exactly

https://github.com/luckyycode/neko-webframework/blob/master/Nova/Cookie.h

its like... you are telling me that webcpp is bad but give me indian code xD

its like... you are telling me that webcpp is bad but give me indian code xD

strong, proof concept of german engineering.

xD

strong, proof concept of german engineering.

xDDD

webcpp is another marvel of brilliant engineering

I am not getting k value,

There is no error

Why?

dat font tho

dat font tho

From mobile compiler

App

After giving input the programme just terminates

Not giving k value

lol what the.. that font

lol what the.. that font

What's wrong