News for hackers. Stuff that matters.
Re:Why is there a “V” in SIGSEGV Segmentation Fault? by waynecochran on Friday June 19, 2020 @03:17PM (#23577935)
I haven't tried this lately, but you get a compiler error if you include <windows.h> and use 'near' and 'far' as variables names (which are holdovers when 'near' and 'far' were keywords for ptrs that supported segmented memory flavors).

A lot of old OpenGL code and uses 'hither' and 'yon' for the near and far clipping plane for this reason. :)

There are no comments on this comment yet.