[MPlayer-dev-eng] fast_memcpy namespace collision

Enrico Weigelt weigelt at metux.de
Mon Jan 19 23:42:18 CET 2004


* D Richard Felker III <dalias at aerifal.cx> [2004-01-19 12:06:02 -0500]:

<snip>
> Send a bugreport to suse or glibc developers (if it's in stock glibc).
> Including a function named fast_memcpy violates ansi or posix or
> something.
Does it really ?
What does POSIX say about functions in the base library ?
Does it specify, that libc may not export other functions than the
supported ones ?


I personally would prefer renaming the function in the mplayer code.
If you'd accept the patch, I'd go ahead and replace fast_memcpy by
_mp_vo_fast_memcpy or something like that.

BTW: wouldn't it be better (for performance) to code this as an inline 
function or a macro ? On most platforms it should be less than 5 ops
(didnt look at the code), so isnt a function call too expensive for
that job ? ... just a dumb question ...


cu
-- 
---------------------------------------------------------------------
 Enrico Weigelt    ==   metux IT services

  phone:     +49 36207 519931         www:       http://www.metux.de/
  fax:       +49 36207 519932         email:     contact at metux.de
  cellphone: +49 174 7066481
---------------------------------------------------------------------
 Diese Mail wurde mit UUCP versandt.      http://www.metux.de/uucp/




More information about the MPlayer-dev-eng mailing list