Displaying 7 results from an estimated 7 matches for "getquality".
Did you mean:
setquality
2007 Dec 17
2
[LLVMdev] PointerType API Change
On Monday 17 December 2007, Christopher Lamb wrote:
> On Dec 17, 2007, at 1:22 AM, Torvald Riegel wrote:
> > Would it be possible to keep get() unchanged, with a default
> > behaviour, plus
> > a warning? Otherwise everybody (assuming everybody gets type void*)
> > will
> > have to update their LLVM passes, and either maintain two versions
> > of the
>
2007 Dec 17
2
[LLVMdev] PointerType API Change
Would it be possible to keep get() unchanged, with a default behaviour, plus
a warning? Otherwise everybody (assuming everybody gets type void*) will
have to update their LLVM passes, and either maintain two versions of the
passes or require their clients to use a certain LLVM version. Then passes
could be "address-space-safe" or not. If the default parameter value for
get() could
2007 Dec 17
0
[LLVMdev] PointerType API Change
On Dec 17, 2007, at 1:22 AM, Torvald Riegel wrote:
> Would it be possible to keep get() unchanged, with a default
> behaviour, plus
> a warning? Otherwise everybody (assuming everybody gets type void*)
> will
> have to update their LLVM passes, and either maintain two versions
> of the
> passes or require their clients to use a certain LLVM version.
AFAIK API
2004 Aug 06
1
SPEEX_GET_QUALITY error
I am embedding speex in boost python
when i execute
int TSpeexEncoder::getQuality() {
int Quality;
speex_encoder_ctl(enc_state,SPEEX_GET_QUALITY,&Quality);
return Quality;
}
i get the error
warning: Unknown nb_ctl request: 5
looking in the header SPEEX_GET_QUALITY is equal to 5
I am able to read all the other settings.
the codec appears to be set...
2007 Dec 17
0
[LLVMdev] PointerType API Change
On Dec 17, 2007, at 2:51 AM, Torvald Riegel wrote:
> On Monday 17 December 2007, Christopher Lamb wrote:
>> On Dec 17, 2007, at 1:22 AM, Torvald Riegel wrote:
>>> Would it be possible to keep get() unchanged, with a default
>>> behaviour, plus
>>> a warning? Otherwise everybody (assuming everybody gets type void*)
>>> will
>>> have to update
2007 Dec 17
0
[LLVMdev] PointerType API Change
On Dec 16, 2007, at 10:22 PM, Anton Korobeynikov wrote:
> Christopher,
>
>> The API for getting PointerType objects has just changed to make
>> Embedded C address space information explicit. The old semantics of
>> PointerType::get() now apply to PointerType::getUnqual(), which
>> returns a pointer in the generic address space. PointerType::get()
>> now
2007 Dec 17
3
[LLVMdev] PointerType API Change
Christopher,
> The API for getting PointerType objects has just changed to make
> Embedded C address space information explicit. The old semantics of
> PointerType::get() now apply to PointerType::getUnqual(), which
> returns a pointer in the generic address space. PointerType::get() now
> requires both a type and an address space.
What is the reason of such change?
--
With best