[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
Re: [xml-dev] XML2.0: Comments (Was: Towards XML 2.0)
- From: Dimitre Novatchev <dnovatchev@gmail.com>
- To: Pete Cordell <petexmldev@codalogic.com>
- Date: Sun, 5 Dec 2010 09:27:45 -0800
> But the problem I see with Mike's <xml:comment/> proposal is that it implies
> that the body of the comment is well-formed. I think this is too onerous if
> you're trying to hack stuff out to see where it's broken, and likely to push
> someone over the edge.
>
> That's what I tried to convey in my example; where the start tag and end tag
> don't match
Who writes XML by hand today? Leave your IDE comment and uncomment
markup for you.
The IDE will know how to do this -- perhaps it will escape/unescape
the characters as necessary, but still display them unescaped in a
suitable color/bgcolor combination.
When trying to uncomment a non-well-formed markup the IDE will:
1. Warn you.
2. Not unescape, in case if you go on.
There are many ways to safely carry out commenting/uncommenting with an IDE.
--
Cheers,
Dimitre Novatchev
---------------------------------------
Truly great madness cannot be achieved without significant intelligence.
---------------------------------------
To invent, you need a good imagination and a pile of junk
-------------------------------------
Never fight an inanimate object
-------------------------------------
You've achieved success in your field when you don't know whether what
you're doing is work or play
On Sun, Dec 5, 2010 at 6:10 AM, Pete Cordell <petexmldev@codalogic.com> wrote:
> Original Message From: "Dave Pawson"
>
>>> There seems to be two main uses of comments in XML today which is
>>> aligned with the two schools of thought in this thread:
>>>
>>> 1.] Simply commenting out code or adding TODOs etc. - similar use to
>>> standard code comments.
>>> ...
>
>> With a KISS hat on, Use Mikes idea,
>> and don't parse them any differently to any other element.
>> That would answer the basic need, 1 above.
>
> But the problem I see with Mike's <xml:comment/> proposal is that it implies
> that the body of the comment is well-formed. I think this is too onerous if
> you're trying to hack stuff out to see where it's broken, and likely to push
> someone over the edge.
>
> That's what I tried to convey in my example; where the start tag and end tag
> don't match:
>
> <!-- Ignore this until I fix it --
> <MyElement>
> <!-- The price is changed by the controller -->
> <price>100.00</price>
> </BrokenMyElement> <!-- Is this the problem? -->
> -->
>
> Pete Cordell
> Codalogic Ltd
> Interface XML to C++ the easy way using C++ XML
> data binding to convert XSD schemas to C++ classes.
> Visit http://codalogic.com/lmx/ or http://www.xml2cpp.com
> for more info
>
>
>
>
> _______________________________________________________________________
>
> XML-DEV is a publicly archived, unmoderated list hosted by OASIS
> to support XML implementation and development. To minimize
> spam in the archives, you must subscribe before posting.
>
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
> subscribe: xml-dev-subscribe@lists.xml.org
> List archive: http://lists.xml.org/archives/xml-dev/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
>
>
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]