Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!news.teledata-fn.de!newsfeed.arcor.de!newsspool3.arcor-online.net!news.arcor.de.POSTED!not-for-mail Content-Type: text/plain; charset="ISO-8859-1" Message-ID: <3072618.pbM1GnOhur@PointedEars.de> From: Thomas 'PointedEars' Lahn Reply-To: Thomas 'PointedEars' Lahn Organization: PointedEars Software (PES) Date: Tue, 18 Oct 2011 19:29:55 +0200 User-Agent: KNode/4.4.11 Content-Transfer-Encoding: 7Bit Subject: Re: Parsing String of Named Function & Converting To Source Newsgroups: comp.lang.javascript References: Followup-To: comp.lang.javascript MIME-Version: 1.0 Lines: 20 NNTP-Posting-Date: 18 Oct 2011 19:29:56 CEST NNTP-Posting-Host: c9eedd44.newsspool1.arcor-online.net X-Trace: DXC=NYLllTCfhE4gP]QSEBQ^d4ic==]BZ:af>4Fo<]lROoR1<`=YMgDjhg2:lDn3Y]T[_5DZm8W4\YJN Why do you try to build an (x)html parser Because it is an interesting problem to solve; `innerHTML' is proprietary, unreliable and undocumented by comparison. I would probably skip the XHTML part, though, because there's DOMParser. > in javascript (@PE: or one of its dialects)? There is no "javascript", so there are no "javascript dialects" :) I might comment on the rest later. PointedEars -- Danny Goodman's books are out of date and teach practices that are positively harmful for cross-browser scripting. -- Richard Cornford, cljs, (2004)