pcp
[Top] [All Lists]

Re: [pcp] pmServiceDiscoveryInterrupt() commit a8b87e2 et al.

To: Dave Brolley <brolley@xxxxxxxxxx>
Subject: Re: [pcp] pmServiceDiscoveryInterrupt() commit a8b87e2 et al.
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Thu, 19 Jun 2014 18:53:58 -0400 (EDT)
Cc: "Frank Ch. Eigler" <fche@xxxxxxxxxx>, pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <53A34633.2040006@xxxxxxxxxx>
References: <20140619194444.3B03D58015@xxxxxxxx> <53A34633.2040006@xxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: BjJB7wia5mHaG5wwZO+OTZP7Ese92A==
Thread-topic: pmServiceDiscoveryInterrupt() commit a8b87e2 et al.

----- Original Message -----
> [...]
> 
> WRT the API, the various options for overloading the current strings
> were considered and discussed and, while I knew that changing the ABI
> could be problematic, it seemed to me that Nathan was encouraging the
> addition of a new options string. This in turn lead me to believe that
> it was not too late to change this API.

Yeah, this PMAPI addition can only be made via a new function.  IIRC
(gettin' old, there's a good chance I'm not RC), I had said something
to the effect that the two externally visible APIs would call a single
internal API, or the old would call the new with NULL options.  If I
didn't, that was the intention - sorry 'bout the ambiguity there.

cheers.

--
Nathan

<Prev in Thread] Current Thread [Next in Thread>