function pointers, closures, lambda

i am only training duty pointers and, i reading k&r section subject, initial thing strike me was, "hey, kinda closure." i knew audacity essentially wrong somehow after hunt online i didn't unequivocally any research comparison.

so since c-style duty pointers essentially opposite closures lambdas? distant i tell fact duty pointer still points tangible (named) duty opposing use anonymously defining function.

why flitting duty function seen some-more comprehensive second case, where unnamed, initial where only normal, bland duty being passed?

please tell me since i am wrong review twin closely.

thanks.