(Come to think of it, "data" would be fine too.)
--John Keiser
> -----Original Message-----
> From: John Keiser [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, August 15, 1998 10:14 AM
> To: Paul Fisher; Classpath
> Subject: RE: New toplevel directory
>
>
> It would work, though perhaps the name resource would better
> describe it. I
> assume the idea is in a binary distribution the resource/
> directory would be
> shipped (almost) verbatim?
> While we're on the topic, I would like to add the top-level directory "vm"
> to the mix, to accomodate this multiple implementation business.
> --John Keiser
>
> > -----Original Message-----
> > From: Paul Fisher [mailto:[EMAIL PROTECTED]]On Behalf Of Paul Fisher
> > Sent: Friday, August 14, 1998 9:28 PM
> > To: [EMAIL PROTECTED]
> > Subject: New toplevel directory
> >
> >
> > I've been running into a problem as of recent, which I believe
> > requires a new toplevel directory.
> >
> > I propose the name be "share" and the directory would have a
> > non-flattened java package naming structure. Resource properties and
> > various other platform-independent files (such as the Unicode
> > database) would reside here -- retrievable through the 1.1
> > getResourse() calls. Installation of the "share" directory would
> > correspond to Autoconf's @datadir@.
> >
> > We can actually call it "data", if everyone prefers that over "share".
> >
> > thoughts?
> >
> > --
> > Paul Fisher * [EMAIL PROTECTED]
> >
> >
>
>
