[Rd] What is the logic behind sys-common, sys-unix et.al. ?

[Prof Brian D Ripley]

On Fri, 1 Jun 2001, Thomas Hoffmann wrote:

> I try to understand how the system specifics are organised in R.
>
> My understanding was that (citing system.txt):
>
>  *	sys-common.c  has code common to the unix/gnome/gnuwin32 ports
>  *	sys-unix.c    has code common to the unix/gnome ports
>  *	system.c      has interface-specific code
>
> But now I see that unix/sys-common contains unix and Win32 specific code which is selected via
> #ifdefs.
>
> Another question is who carries the sys-common file? If it is "common", why does a specific
> system subdir (unix, that is) carry this file?
>
> I know that there are historical reasons for that, but is there a "plan" for reorganising this stuff, now
> that there is at least a third class of systems (macintosh) involved?

Why change what works?

> Another question is: Should the graphics interfaces be connected to the systems in a 1:1 fashion?
> I have a test build of R-1.2.3 for OS/2 an my hard disk which is able to use a Presentation Manager
> and a X11 graphics device: X11 is a 1:1 copy of the unix/X11 files. (And I assume "that new Macs" I
> do not know anything about can display X11, too. And for Win32 exist X11 servers ...)

We do not support X11 on Windows, even though it can be built.

-- 
Brian D. Ripley,                  ripley@stats.ox.ac.uk
Professor of Applied Statistics,  http://www.stats.ox.ac.uk/~ripley/
University of Oxford,             Tel:  +44 1865 272861 (self)
1 South Parks Road,                     +44 1865 272860 (secr)
Oxford OX1 3TG, UK                Fax:  +44 1865 272595

-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-
r-devel mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html
Send "info", "help", or "[un]subscribe"
(in the "body", not the subject !)  To: r-devel-request@stat.math.ethz.ch
_._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._