Thank you for stopping by! I am a full-stack developer that combines the power of entrepreneurship and programming to make the lives of programmers easier.
Sorry for the confusion, I meant explicitly in my project in C.
Thanks for the response!
I do agree that creating functions instead of commenting out a block is better but, creating functions from code blocks that are already readable enough, albeit large but specific enough that they are never gonna be reused is what I think hurts a project. Just this specific case.
From some really good code you extract a function with a lot of parameters that is never going to be reused again will hurt maintainability.
I guess language makes a lot of difference.
Personally I would never create a function with more than two or three parameters, instead I would bundle them into a class.
This can seen like a lot of work but modern Ides can make it easy to do and it usually helps with understanding your problem domain better.
Sorry for the confusion, I meant explicitly in my project in C.
Thanks for the response!
I do agree that creating functions instead of commenting out a block is better but, creating functions from code blocks that are already readable enough, albeit large but specific enough that they are never gonna be reused is what I think hurts a project. Just this specific case.
From some really good code you extract a function with a lot of parameters that is never going to be reused again will hurt maintainability.
I guess language makes a lot of difference.
Personally I would never create a function with more than two or three parameters, instead I would bundle them into a class.
This can seen like a lot of work but modern Ides can make it easy to do and it usually helps with understanding your problem domain better.
There is no difference in the language IMO (except Assembler and COBOL)... :-)