[Pkg-javascript-commits] [node-expat] 08/371: README: markdown fixes
Jonas Smedegaard
dr at jones.dk
Sun Feb 28 09:59:39 UTC 2016
This is an automated email from the git hooks/post-receive script.
js pushed a commit to branch master
in repository node-expat.
commit a10bffc95190c16e3bca66940f2f2c819e94aa73
Author: Astro <astro at spaceboyz.net>
Date: Sat May 22 15:34:16 2010 +0200
README: markdown fixes
---
README.markdown | 13 +++++++------
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/README.markdown b/README.markdown
index 975276a..a18badc 100644
--- a/README.markdown
+++ b/README.markdown
@@ -10,9 +10,9 @@ XML streams? Then you want the fastest XML parser: [libexpat](http://expat.sourc
A stupid speed test is supplied in `bench.js`. We measure how many
25-byte elements a SAX parser can process:
-* [node-xml](http://github.com/robrighter/node-xml) (pure JavaScript): 23000 el/s
-* [libxmljs](http://github.com/polotek/libxmljs) (libxml2 binding): 77000 el/s
-* [node-expat](http://github.com/astro/node-expat) (libexpat binding, this): 113000 el/s
+- [node-xml](http://github.com/robrighter/node-xml) (pure JavaScript): 23,000 el/s
+- [libxmljs](http://github.com/polotek/libxmljs) (libxml2 binding): 77,000 el/s
+- [node-expat](http://github.com/astro/node-expat) (libexpat binding, this): 113,000 el/s
These numbers were recorded on a Core 2 2400 MHz and may turn out to
be bullshit, given my few node.js experience.
@@ -26,9 +26,10 @@ For using the library, make sure `build/default/expat.node` is in
either `$NODE_PATH` or `require.paths`.
So far, three events are emitted by a parser:
-* *startElement* with `name, attrs`
-* *endElement* with `name`
-* *text* with `string`
+
+- *startElement* with `name, attrs`
+- *endElement* with `name`
+- *text* with `string`
Use `test.js` for reference.
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-javascript/node-expat.git
More information about the Pkg-javascript-commits
mailing list