Problem with one-class-per-file approach

[BCS]

Hello Kris,

> Hi folks,
> 
> Is it possible to split the files up to use one class per file again,
> but add a red.xml.xmldom module imports and exposes them somehow?

Take a look at the details of import. IIRC "public import" does something 
like what you want.

> 
> I was hoping it'd be something like the following in the red.xml.dom
> module:
> 
> import red.xml.xmldocument;
> import red.xml.xmlnNode;
> import red.xml.xmlattribute;
> import red.xml.xmlelement;
> import red.xml.xmltextnode;
> import red.xml.xmlcomment;
> import red.xml.xmlcdatasection;
> import red.xml.xmlnodelist;
> import red.xml.xmlattributelist;
> But that doesn't seem to work (I get a whole bunch of "module ... is
> in multiple defined" errors).

I don't know what's causing that, but my first guess would be to add module 
"red.xml.whatever;" lines to each module.

-- 
... <IXOYE><