This is the implementation of
SysUtils.Beep, in sysutils.inc:
{ Beep support }
procedure Beep;
begin
If Assigned(OnBeep) then
OnBeep;
end;
In the
initialization of sysutils, OnBeep is assigned to
SysBeep:
unit sysutils;
{... etc ...}
Initialization
InitExceptions; { Initialize exceptions. OS independent }
InitInternational; { Initialize internationalization settings }
SysConfigDir:='/etc'; { Initialize system config dir }
OnBeep:=@SysBeep;
{... etc ...}
end.
And, finally, SysBeep is simply:
Procedure SysBeep;
begin
Write(#7);
Flush(Output);
end;
Of course, one can replace that for whatever one wants (say, a visual cue for hearing impaired users) but the important thing, regarding this thread, is that OnBeep has
nothing to do with the RichMemo beep or any of the various noises OSs do nowadays. It's just how
Beep is implemented.
And yes, it's probably to take into account computers w/out buzzer, OSs which ignore the chr($07), etc. So you see, in the end we are saying the same thing but from a slightly different point of view.