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
Kris Herlaar:
> Allow me to introduce myself, I'm Kris and new to this list and the D
> language in general,
Welcome here and to D then.
> Being used to (and really liking!) the one-class-per-file approach, I
> instinctively created the classes in seperate files.<
D gives you the freedom, if
Hi folks,
Allow me to introduce myself, I'm Kris and new to this list and the D language
in general, but have well over 20 years of programming experience using several
other languages ranging from Wozniaks' integer basic to Hejlsbergs' c#.
My first venture using D is to create a set of classes
Hi all,
Looks like I just solved my own problem by adding "public:" just above the
imports in red.xml.dom because I got it to work flawlessly just now :)
the dom.d file now looks like this:
module red.xml.dom;
public:
import red.xml.xmlnodelist;
import red.xml.xmlattributelist;
import red.xml
