Re: My Regexp XML Parser -> Structured Perl Data, Cut & Paste Version, No Module's (Vol I)

On Sat, 24 Dec 2005 11:57:13 -0500, "Matt Garrish"
<matthew.garrish@xxxxxxxxxxxx> wrote:

>
><robic0> wrote in message news:kf7pq15pfhs754mu2o2d8fs6meg0h8v2e6@xxxxxxxxxx
>> On Fri, 23 Dec 2005 19:29:45 -0500, "Matt Garrish"
>> <matthew.garrish@xxxxxxxxxxxx> wrote:
>>>Now how about the part where you start dealing with the fact that xml is
>>>not
>>>constrained to single lines. Your little toy has a lot of trouble with:
>>>
>> Huh, constrained to single lines?
>> Wha, where?
>>
>>><!-- comment out this section
>>><oldroot>
>>> <oldstuff>oops!</oldstuff>
>>></oldroot>
>>>-->
>>>
>> Comments are a problem for now. I have a workaround
>> for the near future. I've posted a general complaint
>> about this Regex problem to the general forum.
>>
>>>and also:
>>>
>>><myplace
>>> city="here"
>>> province="there"/>
>>>
>> "white space" is not considered as a seperator yet, only " ". If its
>> xml complieant I will enact it.
>>
>
>Exactly my point. The last XML processor I built took three weeks just to
>write the design for and another 1.5 months to build. And I didn't write my
>own parsers; I used a combination of DOM and SAX parsing. You don't know XML
>and are proud that you've spent four days designing and writing on the fly
>this parser of yours. Are you beginning to see why we don't take you
>seriously.
>
>>
>> Maybe you should not get or use any my software. If I find out you did
>> I will sue you!!!!
>>
>
>Maybe you should consider the legal ramifications of what you've done. You
>posted the code here asking for help fixing it on the premise that it is
>free and open code. By doing so, you've entered an agreement with everyone
>on clpm who responds in any way to your code that this will always be the
>case. Though I don't believe you could ever make a cent off it, bear in mind
>that I have a real cause for legal action if I find out you use this code in
>any commercial product (and that includes reproducing it for an employer).
>
Man you make me laff!

>By the way, have you put any thought into the public interface for this
>thing? It's nice that it runs line-by-line and uses regexes to find tags,
>but that's totally useless for XML parsing. Does it handle events like a SAX
>parser? (Not that I see.) Does it build a parent/child tree? (Again, I don't
>see anywhere that you can tell what the relationship is between any set of
>tags.) Or is this just an exercise in writing regular expressions?
>
>Matt
>
Since its out of sequence, its totally useless for event driven SAX.
However, in-line handling of contents could be re-directed for
special character handling.
Specific accumulation of special "tag" data could be handled too.
You have to think outside the box on this. Definetly the data
structure indenture is right on the money. To modify that data
in-line or pull off just the data you want is no problem.

To tell you the truth, there's a bunch this can do.
You better try to stay off the "negative" machine a little more.
Try the "positive" machine for a while. And oh well, if it flops
who cares, but it punches out some awsome timed data right now.
The technique is new, in my opinion its worth the effort.

Keep the comments coming... I don't care if its negative,
it leads me in the right direction. If I have to swear to get
some feedback so be it.
.

Relevant Pages

  • Re: torture
    ... If you're using Java 1.4 then you already have an XML parser built in to ... manipulable object representation of the XML document in memory. ... The SAX API works by reading the document and generating callbacks to ...
    (comp.lang.java.programmer)
  • Re: XML Parser in EVC++ 4.0
    ... Excuse me can you give me some example for read my file XML with SAX ... parser in EVC++? ...
    (microsoft.public.windowsce.embedded.vc)
  • Re: Getting NASM from C
    ... > format we were going to edit it in... ... all XML is? ... HTML is a specific "subset" of XML for displaying ... it's a text file with "tags" inside ...
    (alt.lang.asm)
  • Re: XmlTextreader versus DOM
    ... I've heard them referred to as "DOM" and "SAX". ... DOM is, generally speaking, the easiest way in which to deal with XML ... "SAX" (named after the original parser, I think) parsers read one XML ...
    (microsoft.public.dotnet.languages.vc)
  • Re: XmlTextreader versus DOM
    ... I've heard them referred to as "DOM" and "SAX". ... DOM is, generally speaking, the easiest way in which to deal with XML ... "SAX" (named after the original parser, I think) parsers read one XML ...
    (microsoft.public.dotnet.xml)