[vorbis-dev] vorbisfile close and memory callbacks

[Firelight Multimedia]

> > This is just wrong, it's not extensive work (far less than the double to
float changeover :)
>
> ...which was absolutely necessary to alleviate pressure on the data cache,
not
> just an interface nicety.  And I'm still, a month later, dealing with
> occasional fallout from that change.  Double->float took two hours.
Repairing
> two vital encode algorithms to not choke on the reduced resolution took
> another month.  I've still not cleaned up all the compiler warnings.

changing from double->float is problematic yes because of the complexities
you state.. search and replace of malloc with if (malloccallback)
malloccallback(..); else malloc(..); ... isnt

this ISNT an interface nicety.. its essential for systems that need to use
memory pools and replace bad memory managers that come with some compilers
(ie consoles) that can have bad fragmentation, no garbage collection and
slow allocation schemes.   (basically we will just have to search and
replace the code ourself on a local copy if this isnt done)

> (Note that I've never had a request for repluggable malloc hooks before,
so  I'm wary of 'like files and memory, there is nothing else'.  Yes, files
is a constant request.)

As i said, -resource usage- is the only thing that really needs to be
managed, memory and file access (and output, which i dont think there is of
any more with no more fprintfs).  I cant see anyone wanting to replace
strcpy etc.. any other stdlib functions only affect speed (like sqrt,log
etc), and thats just a problem with performance which is always acceptable.

> Vorbisfile is a bit different as it's actually a large chunk of example
code that was turned into a library, and the FILE* issue is common to a wide
array
> of applications (indeed, I used FILE* only because it's ANSI where
open/read/write are not, and vorbisfile was an example program).
>
> It is also the case that ogg/vorbis/etc are reference implementations.
They are intended to be very solid, reasonably clear, and easy to maintain.
> They're not intended to be everthing to everyone; simply most things to
most people.
>
> > as i said previously, its an absolute must on console developement ..
you do want EA's support dont you? :)
>
> I want EA's support and I know you were mostly kidding, but I don't like
an offer of support as above being used like a threat.  My development
resources
> are limited, and I'm trying to serve as many people as I can.

Im sorry if you're busy .. i was joking, but i thought this was open source,
it seems like 2 people are the only ones doing anything, so i guess it seems
more like closed source to me :)
my own api has thousands of users with people constantly requesting things ,
i know what its like.

cheers
Brett.

>
> Monty
>
>
>
> --- >8 ----
> List archives:  http://www.xiph.org/archives/
> Ogg project homepage: http://www.xiph.org/ogg/
> To unsubscribe from this list, send a message to
'vorbis-dev-request at xiph.org'
> containing only the word 'unsubscribe' in the body.  No subject is needed.
> Unsubscribe messages sent to the list will be ignored/filtered.
>

--- >8 ----
List archives:  http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to 'vorbis-dev-request at xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is needed.
Unsubscribe messages sent to the list will be ignored/filtered.