Re: [xine-devel] #ifdef LOG and xine->verbosity >= xxx change proposal [sample]

[<bar...@t-...>]

hallo daniel,

> > > 	Anyway, verbosity policy usage is up to UI, so i don't see any
> > > complication here. UI can permit some numeric or "verbosity level
> > > names".
> > 
> > how could a frontend decide how the xine engine interprets verbosity
> > values?
> > 
> > anyway, switching from a numerical comparison (which is the current
> > implementation) to a bit vector intepretation would be an api change
> > (not api syntax but api semantics)
> > 
> 
> 	Okay okay, i will not spend more time with that. The port patch will
> even not go through trashcan.

humm, do i understand you correctly here: you want to discard the whole
patch? in that case i'd apply the good parts of it :-)

guenter

-- 
Succumb to natural tendencies.  Be hateful and boring.