I think that will be a little awkward, actually. What you have now is very clear; if it works, just leave it that way. Why do you think using the return value would represent an improvement?Originally Posted by kr0n1x
I think that will be a little awkward, actually. What you have now is very clear; if it works, just leave it that way. Why do you think using the return value would represent an improvement?
Last edited by MK27; 06-04-2012 at 10:30 AM.
C programming resources:
GNU C Function and Macro Index -- glibc reference manual
The C Book -- nice online learner guide
Current ISO draft standard
CCAN -- new CPAN like open source library repository
3 (different) GNU debugger tutorials: #1 -- #2 -- #3
cpwiki -- our wiki on sourceforge
A lot of the recursive functions I've been using have returns (for example those with trees and lists management). Since I was not able to make it with returns (in this exercise), I was curious to know if the reason was behind my lack of experience or if, as you said, it is actually better to make it without returns.
If you say this is a good solution, it's ok to me xD
Thanks!
