From: Denis Kenzior <denkenz@gmail.com>
To: ell@lists.01.org
Subject: Re: [PATCH 1/3] main: Manually initialize and clean up the main loop
Date: Wed, 08 Jun 2016 13:31:36 -0500 [thread overview]
Message-ID: <57586488.4010005@gmail.com> (raw)
In-Reply-To: <alpine.OSX.2.20.1606081023230.16651@mjmartin-mac01.local>
[-- Attachment #1: Type: text/plain, Size: 1118 bytes --]
Hi Mat,
>>
>> Can you do me a favor and split these into three patches, according to
>> HACKING 'Submitting Patches'.
>
> What do you know, "patches should be split even if breaking compilation
> is unavoidable". Curious about why this is (I'm not lobbying for a
> change, it's just not self-evident).
>
We hardly ever use git bisect, so readability of commits trumps the
breaking of compilation.
>>
>> I wonder if returning bool here is useful since you never check the
>> return value in any of the actual files that use this.
>
> All of the unit tests and examples exit out of main immediately after
> calling l_main_exit, but that may not be the case for every program.
> l_main_exit will do nothing if the main loop is still running.
>
> l_main_run and l_main_quit's return values are similarly ignored, but
> are potentially useful in a similar way.
>
Fair enough, just curious. Some like to use void *_exit functions
because you can't do anything if stuff fails anyway. I've had this
argument with myself many times and don't really have a preference.
Regards,
-Denis
prev parent reply other threads:[~2016-06-08 18:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 22:30 [PATCH 1/3] main: Manually initialize and clean up the main loop Mat Martineau
2016-06-07 22:30 ` [PATCH 2/3] signal: Propagate watch_add errors in l_signal_create Mat Martineau
2016-06-08 13:53 ` Denis Kenzior
2016-06-07 22:30 ` [PATCH 3/3] timeout: Propagate watch_add errors in l_timeout_create functions Mat Martineau
2016-06-08 13:53 ` Denis Kenzior
2016-06-08 13:49 ` [PATCH 1/3] main: Manually initialize and clean up the main loop Denis Kenzior
2016-06-08 18:23 ` Mat Martineau
2016-06-08 18:31 ` Denis Kenzior [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=57586488.4010005@gmail.com \
--to=denkenz@gmail.com \
--cc=ell@lists.01.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.