linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Anderson Lizardo" <anderson.lizardo@gmail.com>
To: linux-sparse@vger.kernel.org
Subject: spyparse - sparse reimplemented in Python
Date: Fri, 30 May 2008 20:39:36 -0400	[thread overview]
Message-ID: <5b5833aa0805301739o6ceb14a6ha84271b938ee70ed@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1400 bytes --]

Hi,

Yesterday I had the (crazy?) idea or reimplementing sparse in Python.
Some personal reasons for doing so:

1) Learn/experiment how to implement some "advanced" data structures in Python
2) Learn more about sparse internals along the way
3) some others I might not remember

Attached is a tarball containing the very very initial code. It
doesn't do anything useful, but should run without errors. A lot of
functions are not implemented yet (I started by sparse_initialize()
and going down until the lower level functions).

Some notes:

- I decided to take a more pragmatic approach and start implementing
only those functions necessary for writing a test-*.c like backend
- For now I'm just doing a plain manual translation of the sparse C
code to Python, thus forcing me to read the entire sparse code (which
IMHO is a good thing for achieving reason (2))
- Along the way I'm rewriting some code to become more OO-friendly
(with classes, methods etc.), therefore while the code is not finished
you will see a lot of mixed procedural and OO code
- I'm newbie in Python coding, so be prepared to see some examples of
bad coding style :)

I cannot guarantee spyparse will have all features from spase (even
because I do it in my free time, which is shared with other projects),
but right now I'm having a lot of fun working on it!

Comments/suggestions are welcome. Regards,
-- 
Anderson Lizardo

[-- Attachment #2: spyparse-0.tar.gz --]
[-- Type: application/x-gzip, Size: 9367 bytes --]

             reply	other threads:[~2008-05-31  0:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-31  0:39 Anderson Lizardo [this message]
2008-06-01 20:33 ` spyparse - sparse reimplemented in Python Pavel Roskin
2008-06-01 23:24   ` Anderson Lizardo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5b5833aa0805301739o6ceb14a6ha84271b938ee70ed@mail.gmail.com \
    --to=anderson.lizardo@gmail.com \
    --cc=linux-sparse@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).