>>3
nESTED FUNCTIONS IN C ARE NOT A STANDARD FEATURE. yOU SHOULD HAD MENTIONED THE RELEVANT IMPLEMENTATION DETAILS, NEVERTHELESS I'LL ASSUME YOU'RE USING gnu c WHICH USES THIS. yOUR MAJOR CONCERNS HERE ARE THESE: 1- iF YOU'RE WORRYING ABOUT EFFICIENCY (AND YOU'VE NOTICED SOME BOTTLENECK OBVIOUSLY), YOU WON'T HAVE THE OPTION TO REWRITE THE PROJECT FROM SCRATCH USING A DIFFERENT IMPLEMENTATION, WHAT YOU'RE GOING TO DO IS A SOLO TO FIND THE IMPLEMENTATION-DETAILS OF THE PARTICULAR IMPLEMENTATION YOU'RE SUBMITTING TO, NAME gnu c, AND FIND HOW THEY'RE IMPLEMENTING THINGS. yOU CAN IMAGINE YOU'RE fUCKED (NOTE THE CAPITALIZATION ON THE WORD), BECAUSE THE REST WILL SIMPLY BLAME YOU. pROJECT GETS MORE REFUNDS, YOU'RE FIRED, SALAM FROM INDIA IS HIRED. cU! yES MOTHERFUCKER, NESTED C FUNCTIONS MIGHT CAUSE JOB LOSS FROM INDIAN CHOCOLATE SMALL(SMELLY?) MAN. cl - NOW i DIGG THAT SHIT. 2- yOU'RE MAKING YOUR SOFTWARE COMPLETELY SUBMITTED TO GNU - THERE'S OBVIOUSLY NO WAY ANYONE ELSE OTHER THAN GNU HAS IMPLEMENTED gnu c (nOTE I'M TALKING ABOUT THE GNU EXTENSION OF C, NOT THE LIBC, ACTUALLY, IF YOU HAVEN'T REALIZED THAT BY NOW, YOU'VE COMPLETELY MISUNDERSTOOD EVERYTHING I WROTE AND YOU'RE BY FAR MOST CONFUSED BY NOW. FUCK YOU!). tHAT MAKES IT GNU SOFTWARE. iF THAT'S FINE BY YOU, KEEP DOING IT. 3- tHIS IS NOT SO POPULAR AMONG SOFTWARE, IT MIGHT BE LIKELY THAT YOU ACTUALLY OBFUSCATE THINGS (AT LEAST, TO OTHERS THEY SEEM OBFUSCATED), AND YOU'RE ALSO COMMITING YOURSELF TO THEM, WHICH MEANS YOU MIGHT NOT BE ABLE TO GO BACK TO "NORMAL" c. iF YOU REMEMBER PREVIOUSLY i MADE AN ASSUMPTION THAT YOU'RE USING gnu c. rEGARDLESS OF WHAT YOU ACTUALLY USE, ALL THIS TEXT UP TO NOW APPLIES.