9 More Discussions You Might Find Interesting
1. HP-UX
I require Hpux 11iv3 administration document if anyone could assist with the same it would be a great help. The Hp site does not have any consolidated document that could be referred to. I require something in line that could assist with network configuration and more. I require the same for Build... (3 Replies)
Discussion started by: kpatel786
3 Replies
2. Shell Programming and Scripting
Hi ,
My chunk of code is as follows:
create_db(){
isql -Usa -Paaa123 -S$DB_SERVER <<- BOF
sp_addlogin $Conf, aaa123
go
sp_addlogin mb, aaa123
go
create database $Conf on $DATA_DEVICE=800 log on $LOG_DEVICE=200
go
online database $Conf
BOF
isql -U$2 -Paaa123 -S$DB_SERVER -D$2... (5 Replies)
Discussion started by: sankasu
5 Replies
3. HP-UX
I'm sharing this in case anybody needs it. Modified from the original solaris pwage script. This modified hpux script will check /etc/password file on hpux trusted systems search /tcb and grep the required u_succhg field. Calculate days to expiry and notify users via email.
original solaris... (2 Replies)
Discussion started by: sparcguy
2 Replies
4. Shell Programming and Scripting
Can we use a here document inside a here document?
Something like this
ssh user@remotehost << REMOTE
sudo vserver vsernamename enter << VSERVER
perform actions on vserver.
VSERVER
REMOTE (6 Replies)
Discussion started by: mnanavati
6 Replies
5. Programming
sorry if i repost this...
hi.. i want to ask how to open pdf files using C in Linux
in Windows, i just use this code:
ShellExecute(GetDesktopWindow(), "open", "D:\\Folder\\File.pdf", NULL, NULL, SW_SHOWNORMAL);
thanks for advance... (3 Replies)
Discussion started by: sunardo
3 Replies
6. Shell Programming and Scripting
$ cat test
a b c d e
f g h i j
k l m n
FILE *p;
p = fopen("a.text","r")
int a;
while ( (a = fgetc(p)) != EOF ) {
printf ("current character is %c \n",a);
}
the code above only prints the first line of the file
a b c d e
i don't know why it doesn't go through the whole... (1 Reply)
Discussion started by: bonosungho
1 Replies
7. Shell Programming and Scripting
I am running HPUX and using WLM (workload manager). I want to write a script to fork CPUs to basically take CPUs from other servers to show that the communication is working and CPU licensing is working. Basically, I want to build a script that will use up CPU on a server. Any ideas? (2 Replies)
Discussion started by: cpolikowsky
2 Replies
8. UNIX for Dummies Questions & Answers
Hi All,
I'm really new to Unix scripts and commands but i think i'm eventually getting the hang of some of it.
I have a task which is to create some kind of script which compares the file names in a directory, with the associated file name in a .txt file. We send out some data and Unix has a... (1 Reply)
Discussion started by: gman
1 Replies
9. Programming
For a job I have to do, I have to design a .tga file reader, however I have had no prior experience in this area, so I was wondering what would be the best language to use to develop my .tga reader ?
many thanks (1 Reply)
Discussion started by: JamesGoh
1 Replies
QXmlLexicalHandler(3qt) QXmlLexicalHandler(3qt)
NAME
QXmlLexicalHandler - Interface to report the lexical content of XML data
SYNOPSIS
All the functions in this class are reentrant when Qt is built with thread support.</p>
#include <qxml.h>
Inherited by QXmlDefaultHandler.
Public Members
virtual bool startDTD ( const QString & name, const QString & publicId, const QString & systemId ) = 0
virtual bool endDTD () = 0
virtual bool startEntity ( const QString & name ) = 0
virtual bool endEntity ( const QString & name ) = 0
virtual bool startCDATA () = 0
virtual bool endCDATA () = 0
virtual bool comment ( const QString & ch ) = 0
virtual QString errorString () = 0
DESCRIPTION
The QXmlLexicalHandler class provides an interface to report the lexical content of XML data.
The events in the lexical handler apply to the entire document, not just to the document element, and all lexical handler events appear
between the content handler's startDocument and endDocument events.
You can set the lexical handler with QXmlReader::setLexicalHandler().
This interface's design is based on the the SAX2 extension LexicalHandler.
The interface provides the startDTD(), endDTD(), startEntity(), endEntity(), startCDATA(), endCDATA() and comment() functions.
See also the Introduction to SAX2.
See also QXmlDTDHandler, QXmlDeclHandler, QXmlContentHandler, QXmlEntityResolver, QXmlErrorHandler, and XML.
MEMBER FUNCTION DOCUMENTATION
bool QXmlLexicalHandler::comment ( const QString & ch ) [pure virtual]
The reader calls this function to report an XML comment anywhere in the document. It reports the text of the comment in ch.
If this function returns FALSE the reader stops parsing and reports an error. The reader uses the function errorString() to get the error
message.
bool QXmlLexicalHandler::endCDATA () [pure virtual]
The reader calls this function to report the end of a CDATA section.
If this function returns FALSE the reader stops parsing and reports an error. The reader uses the function errorString() to get the error
message.
See also startCDATA() and QXmlContentHandler::characters().
bool QXmlLexicalHandler::endDTD () [pure virtual]
The reader calls this function to report the end of a DTD declaration, if any.
If this function returns FALSE the reader stops parsing and reports an error. The reader uses the function errorString() to get the error
message.
See also startDTD().
bool QXmlLexicalHandler::endEntity ( const QString & name ) [pure virtual]
The reader calls this function to report the end of an entity called name.
For every startEntity() call, there is a corresponding endEntity() call. The calls to startEntity() and endEntity() are properly nested.
If this function returns FALSE the reader stops parsing and reports an error. The reader uses the function errorString() to get the error
message.
See also startEntity(), QXmlContentHandler::skippedEntity(), and QXmlSimpleReader::setFeature().
QString QXmlLexicalHandler::errorString () [pure virtual]
The reader calls this function to get an error string if any of the handler functions returns FALSE.
bool QXmlLexicalHandler::startCDATA () [pure virtual]
The reader calls this function to report the start of a CDATA section. The content of the CDATA section is reported through the
QXmlContentHandler::characters() function. This function is intended only to report the boundary.
If this function returns FALSE the reader stops parsing and reports an error. The reader uses the function errorString() to get the error
message.
See also endCDATA().
bool QXmlLexicalHandler::startDTD ( const QString & name, const QString & publicId, const QString & systemId ) [pure virtual]
The reader calls this function to report the start of a DTD declaration, if any. It reports the name of the document type in name, the
public identifier in publicId and the system identifier in systemId.
If the public identifier is missing, publicId is set to QString::null. If the system identifier is missing, systemId is set to
QString::null. Note that it is not valid XML to have a public identifier but no system identifier; in such cases a parse error will occur.
All declarations reported through QXmlDTDHandler or QXmlDeclHandler appear between the startDTD() and endDTD() calls.
If this function returns FALSE the reader stops parsing and reports an error. The reader uses the function errorString() to get the error
message.
See also endDTD().
bool QXmlLexicalHandler::startEntity ( const QString & name ) [pure virtual]
The reader calls this function to report the start of an entity called name.
Note that if the entity is unknown, the reader reports it through QXmlContentHandler::skippedEntity() and not through this function.
If this function returns FALSE the reader stops parsing and reports an error. The reader uses the function errorString() to get the error
message.
See also endEntity() and QXmlSimpleReader::setFeature().
SEE ALSO
http://doc.trolltech.com/qxmllexicalhandler.html http://www.trolltech.com/faq/tech.html
COPYRIGHT
Copyright 1992-2007 Trolltech ASA, http://www.trolltech.com. See the license file included in the distribution for a complete license
statement.
AUTHOR
Generated automatically from the source code.
BUGS
If you find a bug in Qt, please report it as described in http://doc.trolltech.com/bughowto.html. Good bug reports help us to help you.
Thank you.
The definitive Qt documentation is provided in HTML format; it is located at $QTDIR/doc/html and can be read using Qt Assistant or with a
web browser. This man page is provided as a convenience for those users who prefer man pages, although this format is not officially
supported by Trolltech.
If you find errors in this manual page, please report them to qt-bugs@trolltech.com. Please include the name of the manual page
(qxmllexicalhandler.3qt) and the Qt version (3.3.8).
Trolltech AS 2 February 2007 QXmlLexicalHandler(3qt)