Okay, I checked the ISO 9899 standard and yes, you're, it is defined that if the main reach the } and should return a compatible type, then it returns 0. Don't know why it was only an extension in my mind. I was aware that it is the case in C++, but was not sure for the C.
Anyway, I still consider omitting as a bad practice. You only avoid typing few chars and create doubt in the mind of non-experts. Instead, adding it is explicit and does not create any doubt to anyone. Also, my others changes are still valid. Le ven. 7 mars 2025 à 08:22, Schindler, Dietmar - OTPS < [email protected]> a écrit : > From: busybox <[email protected]> On Behalf Of Nop > Sent: Thursday, March 6, 2025 4:33 PM > > ... > > I sent that more or less same patch months ago, which was included in > buildroot. > > The difference with my patch is that I also removed the 2>/dev/null > redirection > > so that it does not hide the issue and I added a return zero because > AFAIK the C > > programming does not allow the main to omit the return, ... > > Since C99, i. e. about 25 years: > > Program termination > 1 ... reaching the } that terminates the main function returns a value of > 0. > > -- > Best regards, > Dietmar Schindler > ________________________________ > manroland Goss web systems GmbH | Managing Director: Franz Kriechbaum > Registered Office: Augsburg | Trade Register: AG Augsburg | HRB-No.: 32609 > | VAT: DE815764857 > > Confidentiality note: > This message and any attached documents may contain confidential or > proprietary information of manroland|Goss. These materials are intended > only for the use of the intended recipient. If you are not the intended > recipient of this transmission, you are hereby notified that any > distribution, disclosure, printing, copying, storage, modification or the > taking of any action in reliance upon this transmission is strictly > prohibited. Delivery of this message to any person other than the intended > recipient shall not compromise or waive such confidentiality, privilege or > exemption from disclosure as to this communication. If you have received > this communication in error, please immediately notify the sender and > delete the message from your system. All liability for viruses is excluded > to the fullest extent permitted by law. > ________________________________ > _______________________________________________ > busybox mailing list > [email protected] > https://lists.busybox.net/mailman/listinfo/busybox >
_______________________________________________ busybox mailing list [email protected] https://lists.busybox.net/mailman/listinfo/busybox
