[Ffmpeg-devel] [PATCH] near is a special keyword

Rich Felker dalias
Wed Mar 1 21:23:06 CET 2006

On Wed, Mar 01, 2006 at 08:01:34AM -1000, Steve Lhomme wrote:
> M?ns Rullg?rd wrote:
> >Steve Lhomme <steve.lhomme at free.fr> writes:
> >
> >>Michael Niedermayer wrote:
> >>>Hi
> >>>On Tue, Feb 28, 2006 at 03:42:26PM -1000, Steve Lhomme wrote:
> >>>>...on some windows compilers (far vs near pointers). So I renamed
> >>>>items called "near".
> >>>#define near smallandstinkingsoft_not_knowing_c_standard
> >>This is exactly like renaming onenear to
> >>smallandstinkingsoft_not_knowing_c_standard. Which I already do.
> >
> >No it's not.
> Yes it is.

No it's not. You are changing the code. Michael said to add a #define
to the platform-specific crap for your Windows build to work around
the bug in MSVC.

> >>I just thought you might want the fix.
> >
> >The fix should go where the bug is, i.e. in the compiler.  If they
> >needed a new keyword they should have used __near.
> Too bad, that keyword existed before Linux was even started.

Stupid fucking windows kids. The keyword has NEVER existed and will
never exist (most likely anyway) in the C language. It exists in
broken Microsoft bastardizations of the C++ language which are adapted
to also compile a limited subset of C code, sometimes incorrectly.

FYI gcc existed long before MSVC.


More information about the ffmpeg-devel mailing list