search for: functioin

> Oh, you're right, inband handling is different, but it's a matter of one > flag, passed to functioin. Probably not that much to keep code DRY. Well, let's first merge your code and then we'll see about possible simplifications. >> frame: 20 ms encoding >> sub-frame: 5 ms encoding (internal) >> layer: one frame of nb or sb >> sb: sub-band >> wb: nb+sb >&gt...

Hi, I''m looking at the rails cookbook for uploading files[1]. At the bottom of the page it says that the sanitize_filename functioin would probably go in a helper or a library. I wonder where these files would be or what they would be called. Pehaps there are some conventions I need to know about? Thanks, Peter [1] http://manuals.rubyonrails.com/read/chapter/78

> Ok, here is cleaned up and fixed version. > > * Function is named speex_get_num_frames() now and return > number of frames, as you suggested. > * WB layers sizes are taken from wb_skip_table[], while NB frame > sizes are calculated with speex_mode_query(). Looking better. Just make sure to remove the stuff that isn't C99-compatible (e.g. // comments). > I've

Alexander Chemeris wrote: > On 2/16/08, Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> wrote: >>> Oh, you're right, inband handling is different, but it's a matter of one >>> flag, passed to functioin. Probably not that much to keep code DRY. >> Well, let's first merge your code and then we'll see about possible >> simplifications. > > Waiting for your decision ;) > I guess you stopped on the fact you need to check my statement > about wb_skip_table? Oh, your ta...

We process very large programs and it is not unusual for the IR for some compilation unit to exceed system memory. With some hacking in LLVM 2.5 I was able to coax LLVM to generate asm for each functioin as it was processed and then completely forget about it (i.e. delete it) and move on to the next function. This required a bit of hackery. I had to create two pass managers, one for the module and one for each function. I called doInitialization on the module pass manager to convince the AsmPrin...

...in > > nb_decode() instead of duplicating code. > > Well, the code is a bit different (e.g. handling of in-band data), so > I'm not sure it's possible in a way that is worth it. Oh, you're right, inband handling is different, but it's a matter of one flag, passed to functioin. Probably not that much to keep code DRY. > frame: 20 ms encoding > sub-frame: 5 ms encoding (internal) > layer: one frame of nb or sb > sb: sub-band > wb: nb+sb > uwb: nb+sb+sb Hum... Then SPEEX_SUBMODE_BITS_PER_FRAME macro have wrong name. This is what I was trying to ask in m...

On 2/16/08, Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> wrote: > > Oh, you're right, inband handling is different, but it's a matter of one > > flag, passed to functioin. Probably not that much to keep code DRY. > > Well, let's first merge your code and then we'll see about possible > simplifications. Waiting for your decision ;) I guess you stopped on the fact you need to check my statement about wb_skip_table? > >> frame: 20 ms encodin...

...Valin <jean-marc.valin@usherbrooke.ca> wrote: > Alexander Chemeris wrote: > > On 2/16/08, Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> wrote: > >>> Oh, you're right, inband handling is different, but it's a matter of one > >>> flag, passed to functioin. Probably not that much to keep code DRY. > >> Well, let's first merge your code and then we'll see about possible > >> simplifications. > > > > Waiting for your decision ;) > > I guess you stopped on the fact you need to check my statement > > abou...

...IR files that could then be code-generated separately? -- John T. David Greene wrote: > We process very large programs and it is not unusual for the IR for some > compilation unit to exceed system memory. With some hacking in LLVM 2.5 > I was able to coax LLVM to generate asm for each functioin as it was > processed and then completely forget about it (i.e. delete it) and move > on to the next function. > > This required a bit of hackery. I had to create two pass managers, one > for the module and one for each function. I called doInitialization on > the module pass ma...