however ACPI is simpler then C++

notice how ACPI is the worst standard i've ever seen

notice how every one of your computers has an implementation of ACPI

notice how ACPI is the worst standard i've ever seen

it is not even close

Did you work with WinAPI? :D

How about you implement ACPI on CLINL?

no i would not code in either C OR C++ for fun

don't claim that you are better than qneko if you don't even know about lambda calculus

i do know about it but have yet to find a practical use for it

if he found a practical use for it i am more then happy to hear it

std::thread

i am beginner in c programming. what is best way to learn c? which book do you recommend to a beginner?

i am beginner in c programming. what is best way to learn c? which book do you recommend to a beginner?

you are likely refering to lambda functions in C++

i am beginner in c programming. what is best way to learn c? which book do you recommend to a beginner?

however lambdas in C++ still have a much simpler syntax and allows you to do imperative programming inside it

i find pthread_t easier to use

LAMBDAS ARE SYNTAX SUGAR

Facepalm

100 ?

Not that much in fact, I guess it may be due to hardware stream operations: ripemd160 494.92k ( 2.02µs) (± 4.33%) 224 B/op 1.18× slower MD4 585.44k ( 1.71µs) (± 3.79%) 224 B/op fastest MD5 575.92k ( 1.74µs) (± 4.23%) 224 B/op 1.02× slower SHA1 556.56k ( 1.8µs) (± 5.28%) 224 B/op 1.05× slower SHA224 491.0k ( 2.04µs) (± 3.62%) 224 B/op 1.19× slower SHA256 495.62k ( 2.02µs) (± 4.55%) 240 B/op 1.18× slower SHA384 416.7k ( 2.4µs) (± 3.40%) 256 B/op 1.40× slower SHA512 404.13k ( 2.47µs) (± 3.36%) 272 B/op 1.45× slower

in C++ basically yes

Actually... average functions are sugar, cause names are gone after the compilation :D

does std::thread have semaphores?

https://en.cppreference.com/w/cpp/thread/condition_variable

names are not actually fully gone most of the time

no i mean a real semaphore

Interface function names are not gone

semaphores act as mutexs and do not require a mutex inside the implementation of it

MMMMh in think not, but given implementation of one is less than 35 LoC it is not an issue

A mutex is a binary semaphore

A recursive mutex is a semaphore, then? :D

Any mutex is one

No, I mean... identical to a semaphore?

a semaphore is basically an std::atomic int

ya we need them to signal when every camera finishes reading and finding all the points of interest

std::condition_variable fits the role

Or a future if you're dumb :D

Or a future if you're dumb :D

std::condition_variable fits the role