Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:65708 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 12601 invoked from network); 7 Feb 2013 09:31:37 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Feb 2013 09:31:37 -0000 Authentication-Results: pb1.pair.com smtp.mail=mike.php.net@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=mike.php.net@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.47 as permitted sender) X-PHP-List-Original-Sender: mike.php.net@gmail.com X-Host-Fingerprint: 209.85.215.47 mail-la0-f47.google.com Received: from [209.85.215.47] ([209.85.215.47:34660] helo=mail-la0-f47.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 0B/65-10737-77473115 for ; Thu, 07 Feb 2013 04:31:36 -0500 Received: by mail-la0-f47.google.com with SMTP id fj20so2347669lab.20 for ; Thu, 07 Feb 2013 01:31:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=S2UUl53I4rRPwFt8YWHRzTrssIpCvL812/fZkrKifbY=; b=GzYK2twi8PLH5gWoAVVXL+6XFV9b2NVNU8U7KihTqEI8logADKQDJheeA0EIlJrJZA VEZXWPdCFGTouXOnabmltEZN4AKS1islW8jB4/H3l1Dg5WT/CdFk2nm3dvhXWiB9dcpb 7eFZK0kBwuAnXL9d9xbROjQaOIwoB9wkwdrZcfw2da+CQ9hFYqIq8IQL6NCkvnJ+qnrC LyNnqvJO/qsQ9Aa4osb1fX9+MuCIaP9IoUJso7UbB1JKcfifMf3bA4zfNclpi80ztHn4 m2ZEAijH3JCGbgxknyxxISMgYWOv1fMSPWHzq/NSRV2tVfqeY3+x8Db3GHOhNqlY8o/b QUvw== MIME-Version: 1.0 X-Received: by 10.112.16.102 with SMTP id f6mr500122lbd.3.1360229492082; Thu, 07 Feb 2013 01:31:32 -0800 (PST) Sender: mike.php.net@gmail.com Received: by 10.114.98.231 with HTTP; Thu, 7 Feb 2013 01:31:31 -0800 (PST) In-Reply-To: <511367CC.2020800@2bepublished.at> References: <94A38011-0897-4A35-AA1B-5787255C432D@gmail.com> <511367CC.2020800@2bepublished.at> Date: Thu, 7 Feb 2013 10:31:31 +0100 X-Google-Sender-Auth: Cet-aU9hUNdfCgxMB4LSIFV3zWg Message-ID: To: Christoph Rosse Cc: Alexey Zakhlestin , Keyur Govande , internals@lists.php.net Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] [RFC] Improved Linux process title support in the CLI SAPI From: mike@php.net (Michael Wallner) On 7 February 2013 09:37, Christoph Rosse wrote: > Am 2013-02-07 08:45, schrieb Alexey Zakhlestin: > >> >> On 07.02.2013, at 9:40, Keyur Govande wrote: >> >>> Hello, >>> >>> I've created a new RFC to improve support for setting a CLI process' >>> title >>> on Linux. It is based off of the PostgreSQL implementation and is more >>> robust than the proctitle extension. >>> >>> More details and patch here: https://wiki.php.net/rfc/cli_process_title >> >> >> This would be useful for some of my tasks! >> I don't like names of functions, but I like functionality and API approach >> >> how about: >> >> bool cli_title_settable(void); This function name is ambiguous, does it mean set table or is settable, I guess it means the latter, so it should also be named like that. >> bool cli_title_set(string); >> string cli_title_get(); >> >> > > Greate feature and +1 to Alexeys function names. > > But what is the point in checking if I'm able to set a title with > is_cli_ps_title_available() if set_cli_ps_title() can fail and return false > anyway? > > I'm just asking because I don't see the benefit of the function > is_cli_ps_title_available for the user. > > > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > -- Regards, Mike