25 messages in org.ibiblio.lists.xom-interest[XOM-interest] Three cosmetic patches
FromSent OnAttachments
Wolfgang HoschekFeb 9, 2004 6:42 pm 
Elliotte Rusty HaroldFeb 10, 2004 9:25 am 
Wolfgang HoschekFeb 10, 2004 3:23 pm 
jco...@reutershealth.comFeb 10, 2004 3:48 pm 
Elliotte Rusty HaroldFeb 11, 2004 1:21 pm 
Wolfgang HoschekFeb 11, 2004 1:24 pm 
jco...@reutershealth.comFeb 11, 2004 2:15 pm 
Elliotte Rusty HaroldFeb 11, 2004 3:18 pm 
jco...@reutershealth.comFeb 11, 2004 4:20 pm 
Francois BeausoleilFeb 11, 2004 8:08 pm 
Trimmer, ToddFeb 12, 2004 11:57 am 
Elliotte Rusty HaroldFeb 12, 2004 2:53 pm 
Trimmer, ToddFeb 13, 2004 1:26 pm 
Elliotte Rusty HaroldMar 8, 2004 3:17 pm 
jco...@reutershealth.comMar 8, 2004 4:06 pm 
Elliotte Rusty HaroldMar 8, 2004 4:34 pm 
Elliotte Rusty HaroldMar 9, 2004 11:55 am 
Bradley S. HuffmanMar 9, 2004 12:09 pm 
Elliotte Rusty HaroldMar 9, 2004 1:05 pm 
jco...@reutershealth.comMar 9, 2004 2:04 pm 
jco...@reutershealth.comMar 9, 2004 4:32 pm 
Elliotte Rusty HaroldMar 9, 2004 10:43 pm 
John CowanMar 9, 2004 10:58 pm 
Elliotte Rusty HaroldMar 10, 2004 6:12 am 
Dirk BergstromMar 10, 2004 6:25 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[XOM-interest] Three cosmetic patchesActions...
From:Trimmer, Todd (todd@trizetto.com)
Date:Feb 13, 2004 1:26:37 pm
List:org.ibiblio.lists.xom-interest

OK, this sounds like the right amount of conservatism. I won't be able to make a solid case for making them public until after 1.0, anyway. I might be able to get away with using Serializer. As long as when I call write(Element) I am not forced to use nu.xom.Serializer's way of traversing to sub-content, I should be fine.

Todd Trimmer

-----Original Message----- From: Elliotte Rusty Harold [mailto:elh@metalab.unc.edu] Sent: Thursday, February 12, 2004 1:40 PM To: Trimmer, Todd Cc: 'xom-@lists.ibiblio.org' Subject: Re: [XOM-interest] Three cosmetic patches

At 9:49 AM -0700 2/12/04, Trimmer, Todd wrote:

So I have to ask why XOM extension writers have to be forced to use the Serialzer interface to get to this power? My serializers will still take arguments like Element, Attribute, etc., but won't necessarily write them in a purely atomic fashion, the way nu.xom.Serializer does.

They aren't public mainly to keep from cluttering the API. Plus there may be some assumptions abut how and when they the methods of TextWriter are called and used that aren't currently enforced directly in the TextWriter code. I'd have to check. If there were a good use case for directly accessing this stuff, I'd consider making them public, though probably not till after 1.0. --

Elliotte Rusty Harold elh@metalab.unc.edu Effective XML (Addison-Wesley, 2003) http://www.cafeconleche.org/books/effectivexml

http://www.amazon.com/exec/obidos/ISBN%3D0321150406/ref%3Dnosim/cafeaulaitA