search for: debated

...If you are not on ogg-dev already and are interested in libogg2 development you should join it now at http://lists.xiph.org/mailman/listinfo/ogg-dev In order to further facilitate everyone's ability to be informed I'm laying out an outline of which changes are actually being made: I. Debated API elements: A. To my last knowledge there was *STILL* a debate going on re discont. codecs, even though these have been published by Monty months ago. A part of this debate the following API additions have been debated: within ogg2_packet struct: ogg_int64_t top_granule;...

...If you are not on ogg-dev already and are interested in libogg2 development you should join it now at http://lists.xiph.org/mailman/listinfo/ogg-dev In order to further facilitate everyone's ability to be informed I'm laying out an outline of which changes are actually being made: I. Debated API elements: A. To my last knowledge there was *STILL* a debate going on re discont. codecs, even though these have been published by Monty months ago. A part of this debate the following API additions have been debated: within ogg2_packet struct: ogg_int64_t top_granule;...

...If you are not on ogg-dev already and are interested in libogg2 development you should join it now at http://lists.xiph.org/mailman/listinfo/ogg-dev In order to further facilitate everyone's ability to be informed I'm laying out an outline of which changes are actually being made: I. Debated API elements: A. To my last knowledge there was *STILL* a debate going on re discont. codecs, even though these have been published by Monty months ago. A part of this debate the following API additions have been debated: within ogg2_packet struct: ogg_int64_t top_granule;...

...If you are not on ogg-dev already and are interested in libogg2 development you should join it now at http://lists.xiph.org/mailman/listinfo/ogg-dev In order to further facilitate everyone's ability to be informed I'm laying out an outline of which changes are actually being made: I. Debated API elements: A. To my last knowledge there was *STILL* a debate going on re discont. codecs, even though these have been published by Monty months ago. A part of this debate the following API additions have been debated: within ogg2_packet struct: ogg_int64_t top_granule;...

...If you are not on ogg-dev already and are interested in libogg2 development you should join it now at http://lists.xiph.org/mailman/listinfo/ogg-dev In order to further facilitate everyone's ability to be informed I'm laying out an outline of which changes are actually being made: I. Debated API elements: A. To my last knowledge there was *STILL* a debate going on re discont. codecs, even though these have been published by Monty months ago. A part of this debate the following API additions have been debated: within ogg2_packet struct: ogg_int64_t top_granule;...

I'm looking for a solution to provide a live stream of the debate on Sofware Patents in Monday's EU Council of Ministers [1]. Here's what I've in mind: * Council --> mobile phone --> software answering machine --> Internet server * Council --> mobile phone --> VOIP --> Internet server Has anyone ever streamed something via a cell phone? How would you realize

I'm just a causual reader of the vorbis@xiph.org list and lately its been flooded with this tagging debate(and the what, 5 threads its spawned?). I think that it is getting way out of hand. I personally don't have anything against the proposal(though i'm not for it) but lately I've been getting double the number of messages I usually do and its really starting to tick me

Currently there is a mixture of indented namespaces and un-indented namespaces in both LLVM and Clang. I think this is confusing and it wastes developer time debating the issue. I'd like to pick one and stick with it consistently. Indenting cannot possibly work in many contexts -- file-wide namespaces just make no sense to indent. So I don't think we should pick "always indent".

Hello everyone, I have been using R to do some behavioural economic analysis for my masters thesis, specifically fitting demand curves using nls. E.g. Formula: y ~ c + b * x - a * exp(x) Parameters: Estimate Std. Error t value Pr(>|t|) c -0.445097 0.080823 -5.507 0.005304 ** b -0.777105 0.059528 -13.054 0.000199 *** a 0.011908 0.003886 3.064 0.037495 * --- Signif.

Dear R Developers, First of all, I would like to thank you Jeroen Ooms for taking the binary Window Builds from Duncan. I firmly believe that the R Community will benefit a lot from his work. However, the debate I would like to open is about if some of Microsoft R Open Code shall be ported from R Open to Mainstream R. There are some beneficts in R Open such as multithreaded performance:

Tried sending this message with the original topic On Mon, 17 Feb 2003, Andreas Aardal Hanssen wrote: > Hi, Ian. Cross-posting discussions like this is usually not appreciated > by those who subscribe to both foras, so I'll limit it to the Dovecot > list. Mea culpa. That was an inadvertent mess-up on my part; I did not see the headers, usually going by the list's reply-to

Hello all, Quick question (possibly!) - I''ve got a few records indexed and doing a search for ''test'' reports in no hits even though I know the word ''tests'' exists in the indexed field. Doing a search for ''tests'' produces a result. I would have thought that ''test'' would match ''tests'' but no such

User here: incorporating Intel's MKL, as MRO does, would be a very welcome addition. I was an MRO user before and it improved my experience with medium data immensely. They did, however, leave behind bugs here and there, especially related to development with Rcpp, so I switched back to vanilla R. On Mon, Oct 30, 2017, 9:42 AM Juan Telleria <jtelleriar at gmail.com> wrote: > Dear

So as long as I can read, OpenBlas, for Windows, might be a worth considering option: http://www.openblas.net But Intel MKL also seems to be free*: https://software.intel.com/en-us/articles/free-mkl Thank you, Juan El 30/10/2017 6:45 p. m., "Avraham Adler" <avraham.adler at gmail.com> escribi?: > [Sent offlist accidentally] > > What concerns me first and foremost is

[Sent offlist accidentally] What concerns me first and foremost is that the licensure would have to be ironclad (including for commercial use like vanilla R now) as well as ensuring that R remains completely FLOSS. Anything ?added? to R has to be a no-strings-attached gift to R. Also, I would think that it would have to play nice with existing workflows (like OpenBLAS instead of MKL) unless

On 29 October 2017 at 22:01, Kenny Bell wrote: | User here: incorporating Intel's MKL, as MRO does, would be a very welcome | addition. | | I was an MRO user before and it improved my experience with medium data | immensely. | | They did, however, leave behind bugs here and there, especially related to | development with Rcpp, so I switched back to vanilla R. With all due respect: You may

Estimados Sobre el registros, por estos lados el registro es o no es necesario, depende la persona, en otros términos, supongamos que pinto un cuadro, lo coloco en las redes sociales, hay publicación, pero luego aparece en la tapa de una revista muy cara, en ese caso hay registros que dicen que soy el autor, puedo reclamar, sin embargo estaría complicado que alguien acepte que yo pinte La

Guys. Im reading a lot about ser, nat, stun, etc. And I noticed there are a lot of ways to get around nat but I would like to hear some success stories about handling nat users with multiple voip phones behind nat. I have my asterisk box behind but ports are forwarded (5060 5004 10000-20000 for rtp and 4569 for iax2) but still.. I can quite figure out what ser and stund have to do on this

On Thu, Jan 10, 2013 at 12:13 PM, Justin Holewinski < justin.holewinski at gmail.com> wrote: > On Thu, Jan 10, 2013 at 2:59 PM, Daniel Berlin <dberlin at dberlin.org>wrote: > >> On Thu, Jan 10, 2013 at 2:18 PM, Justin Holewinski >> <justin.holewinski at gmail.com> wrote: >> > On Thu, Jan 10, 2013 at 1:31 PM, Daniel Berlin <dberlin at dberlin.org>

On 28 Nov 2012, at 17:02, Tanya Lattner wrote: >> 14116 - Inliner incorrectly combines cleanup and catch landing pads > > I think this one can be moved out as a release blocker. Too much debate and no action on the bug in over a month. This bug means that we can't compile at anything over -O1, or we get code that does the wrong thing (e.g. terminate instead of catching an