> I think you are being facetious
Bingo 
> Mostly I was just looking for a little pity
> and also I was looking just to communicate; I have been working on a project based on
> MAME for a year and a half now with almost no outlet to talk about it at all, and
> sometimes I just want to vent because there is no where else to do so.
You certainly should talk about it more. And maybe use the Programming Forum, where it's more on topic (it's not like much else happens there) We're certainly interested in absorbing any really interesting modularizations you come up with (ClientServer's backend is going to get absorbed at some point too, most likely).
> I get tons of memory leaks with the new input system, as reported by valgrind; it
> seems that once the input objects for a given game have been instantiated they kind
> of never go away; I am not sure why. This could certainly be an artifact of the way
> that I am using them, although I don't quite know how. The only objects that I create
> are a global driver_enumerator created with:
I don't know the details here, but Valgrind is fairly clean on current MAME with respect to core leaks. Plenty of drivers do leak here and there, of course, but those get fixed as they're caught.
|
Index 
Flat 
Re: I think this was the necessary part of your post....
Reply
