[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: If XML is too hard for a programmer, perhaps he'd b e bett

• To: Jeff Lowery <Jeff.Lowery@c...>
• Subject: Re: If XML is too hard for a programmer, perhaps he'd b e better off as a crossing guard
• From: Uche Ogbuji <uche.ogbuji@f...>
• Date: Fri, 28 Mar 2003 14:09:24 -0700
• Cc: xml-dev@l...
• In-reply-to: Message from Jeff Lowery <Jeff.Lowery@c...> of "Thu, 27 Mar 2003 15:12:49 PST." <4827EC373E03DB44AC2AB3900430896B02666B@c...>
• Sender: Uche Ogbuji <uche.ogbuji@f...>

> I would add, though, that Uche's article and references describing
> generators has prompted me to by my first Python book; I tried grokking
> Stackless but gave up after the old noggin started throwing sparks like the
> Star Trek bridge deck during a Klingon battle.

Indeed, generators are perhaps the most merciful introduction to continuations 
for a programmer of procedural heritage (as mine was).  I first ran into 
continuations in all their glory in Scheme, and I think the two months of my 
adult life about which I can remember no details must be from the period where 
my brain was recovering from the resultant explosion.

I never *really* grokked continuations until I played with Stackless Python, 
and boy did I regret missing them for so many years.  Then Python decided to 
take up just the generator speciaization of continuations, and I was 
disapointed until I learned two things:

1) Generators offer an almost guaranteed "lightbulb" moment for a decently 
trained programmer (I would measure that for this discussion as one who has 
ever had to code a variety of tree-traversal routines)

2) Once you start to really feel the generator zen, you find that you can do 
most of the cool things that continuations offer using generators along.  
David Mertz has some nice articles on IBM dW about simulating microthreads and 
coroutines using generators.


-- 
Uche Ogbuji                                    Fourthought, Inc.
http://uche.ogbuji.net    http://4Suite.org    http://fourthought.com
Use internal references in XML vocabularies - http://www-106.ibm.com/developerw
orks/xml/library/x-tipvocab.html
Universal Business Language (UBL) - http://www-106.ibm.com/developerworks/xml/l
ibrary/x-think16.html
EXSLT by example - http://www-106.ibm.com/developerworks/library/x-exslt.html
The worry about program wizards - http://www.adtmag.com/article.asp?id=7238
Use rdf:about and rdf:ID effectively in RDF/XML - http://www-106.ibm.com/develo
perworks/xml/library/x-tiprdfai.html
Keep context straight in XSLT - http://www-106.ibm.com/developerworks/xml/libra
ry/x-tipcurrent.html
Using SAX for Proper XML Output - http://www.xml.com/pub/a/2003/03/12/py-xml.ht
ml
SAX filters for flexible processing - http://www-106.ibm.com/developerworks/xml
/library/x-tipsaxflex.html

• References:
  • RE: If XML is too hard for a programmer, perhaps he'd be better off as a crossing guard
    • From: Jeff Lowery <Jeff.Lowery@c...>

• Prev by Date: RE: If XML is too hard for a programmer, perhaps he'd be better off as a crossing guard
• Next by Date: Re: Re: If XML is too hard for a programmer, perhaps he 'd be better off as a crossing guard
• Previous by thread: RE: If XML is too hard for a programmer, perhaps he'd be better off as a crossing guard
• Next by thread: RE: If XML is too hard for a programmer, perhaps he'd be better off as a crossing guard
• Index(es):
  • Date
  • Thread