Martin,
They are actually implemented in the source. What you're seeing is simply no code in the method body.
However, C++ allows you to initialize variables and inherited class constructors in a comma-separated list before the first method body bracket. This is the best way I can think to explain it.
You'll see that XSLTInputSource actually inherits InputSource, so this is calling InputSource's constructor with no parameters. Then, m_stream and m_node member variables are initialized by the value in the parentheses. This appears to setup the XSLTInputSource object just fine.
XSLTInputSource::XSLTInput
InputSource(),
m_stream(stream),
m_node(0)
{
}
XSLTInputSource::XSLTInput
InputSource(),
m_stream(&stream),
m_node(0)
{
}
corey
Main Topics
Browse All Topics
by: jkrPosted on 2005-04-24 at 12:22:51ID: 13854790
>>for anything other than file?
There seems to be a misunderstanding - 'istream' does not necessarily have to represent a file, it can be anything that fits an input stream buffer like 'istream', such as e.g. a 'istrstream'- see http://msdn.microsoft.com/
Apart from that: I don't know XALAN, but according to http://xml.apache.org/xala
# XSLTInputSource (const XMLCh *systemId)
Create a new input source with a system identifier.
# XSLTInputSource (const XalanDOMString &systemId)
Create a new input source with a system identifier.
# XSLTInputSource (const char *systemId)
Create a new input source with a system identifier.
# XSLTInputSource (const char *systemId, const char *publicId)
Create a new input source with a system identifier and a public identifier.
# XSLTInputSource (const XMLCh *systemId, const XMLCh *publicId)
Create a new input source with a system identifier and a public identifier.
# XSLTInputSource (const XalanDOMString &systemId, const XalanDOMString &publicId)
Create a new input source with a system identifier and a public identifier.
# XSLTInputSource (XalanNode *node)
Create a new input source with a DOM node.
# XSLTInputSource (StreamType *stream)
Create a new input source with std stream.