search for: l166

...articularly nice form of Python's tuple-unpacking idiom). Am I missing something? cheers Ben https://github.com/r-devel/r-svn/blob/eac72e66a4d2c2aba50867bd80643b978febf5a3/src/library/stats/R/power.R#L38-L52 https://github.com/r-devel/r-svn/blob/master/src/library/stats/R/family.R#L166-L171

...I can't see a > way of grabbing it after the fact. > > I can see in the code where the right variables are.. > > https://github.com/asterisk/asterisk/blob/master/apps/app_record.c#L140 > dtmf_response > > https://github.com/asterisk/asterisk/blob/master/apps/app_record.c#L166 > * \param dtmf_integer the integer value of the DTMF key received > > So,3 questions I guess: > > 1: Am I going about this the right way? (unimrcp is not an option here) > 2: Can someone explain in layman's terms how a simpleton like me could > copy, hack about with and ma...

...is obviously a larger change. Also if we were going to bump the API version I'd want to at the same time do all the other things we are planning for API 3, and that potentially makes it a much bigger deal: https://github.com/libguestfs/nbdkit/blob/b485ade71464fc351828e2fcce54464709bf234d/TODO#L166 It has the advantage of making it easier to access the export name from sh plugins, since those don't have access to nbdkit_* API calls (or at least we haven't thought about how we would do that). Thoughts? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/...

...;> > >> I can see in the code where the right variables are.. > >> > >> https://github.com/asterisk/asterisk/blob/master/apps/app_record.c#L140 > >> dtmf_response > >> > >> https://github.com/asterisk/asterisk/blob/master/apps/app_record.c#L166 > >> * \param dtmf_integer the integer value of the DTMF key received > >> > >> So,3 questions I guess: > >> > >> 1: Am I going about this the right way? (unimrcp is not an option here) > >> 2: Can someone explain in layman's terms how a s...

...nge. Also if we were > going to bump the API version I'd want to at the same time do all the > other things we are planning for API 3, and that potentially makes it > a much bigger deal: > > https://github.com/libguestfs/nbdkit/blob/b485ade71464fc351828e2fcce54464709bf234d/TODO#L166 Yeah, bumping to API 3 is a much bigger deal; we can get most of the benefits of just letting the plugin know WHICH export name was requested without making that bump. > > It has the advantage of making it easier to access the export name > from sh plugins, since those don't have ac...

...le for that to happen. We don't cope well with this situation. (2) The assert is protecting us from some minimal checks in this code, but I think the right answer is to just add those checks. https://github.com/libguestfs/nbdkit/blob/79b26ee95034d9c90913da3b5db596503c5d03d9/plugins/sh/call.c#L166 Anyway, a possible patch for this is attached, but I'm not very confident it is correct. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com libguestfs lets you edit virtual machines....

This is a major rewrite compared to my v1 series, where I've tried a lot harder to ensure that we still accommodate building on Haiku (although I have not actually yet fired up a Haiku VM to try it for myself). I also managed to make the sh plugin fully parallel, on capable platforms. See also my question on patch 10 on whether I've picked the best naming convention. Eric Blake (17):