From: Mike Krolewski <mkrolewski@rii.com>
Newsgroups: comp.databases.oracle.tools
Subject: Re: PL/SQL for XML parser???
Date: Fri, 02 Feb 2001 20:45:13 GMT
Organization: Deja.com
Lines: 42
Message-ID: <95f68m$kka$1@nnrp1.deja.com>
References: <GJfe6.2095$ln1.180027@newsread2.prod.itd.earthlink.net>
NNTP-Posting-Host: 63.75.139.178
X-Article-Creation-Date: Fri Feb 02 20:45:13 2001 GMT
X-Http-User-Agent: Mozilla/4.0 (compatible; MSIE 5.0; Windows NT; DigExt)
X-Http-Proxy: 1.1 x52.deja.com:80 (Squid/1.1.22) for client 63.75.139.178
X-MyDeja-Info: XMYDJUIDmikkrolewski


In article <GJfe6.2095$ln1.180027@newsread2.prod.itd.earthlink.net>,
  "G" <gennt@hotmail.com> wrote:
> Hi all,
> can I use PL/SQL to write my own parser for XML. I m not think of
 using any
> other languages, just PL/SQL. Any opinions.
>
>
It is possible.

I would not suggest it. There are better ( read already written ) code
for parsing XML files. They often start with a definition of the XML
and it will do all the rest parsing. You need to only add in the code
to decide where to put everything.

And after just developing a parser for a file format using flex/bison,
I would suggest that C/C++ is a much better solution if you are going
to start from scratch. It took 2 weeks to get re-aquainted with parsing
technology, read and learn flex/bison, setup the development
environment, and write and debug the code. Without flex/bison, I know I
would still be building the parser part. And as a performance
comparison, IMHO the flex programs code is faster than anything I would
have developed and is more flexible to changes.

The power of these tools is flexibility. To add more file formats, or
modify how the data is read is extremely simple.


On the other side, PL/SQL is considered a small language. It does not
nor should it have all of the features of large language like C or java
or COBOL. It has many purposes and uses. However, as a general purpose
programming language, PL/SQL is a very poor contender.

--
Michael Krolewski
Rosetta Inpharmatics
mkrolewski@rii.com
              Usual disclaimers


Sent via Deja.com
http://www.deja.com/

