List for cgit developers and users
 help / color / mirror / Atom feed
From: Jason at zx2c4.com (Jason A. Donenfeld)
Subject: RFE: .so filters
Date: Fri, 10 Jan 2014 18:57:57 +0100	[thread overview]
Message-ID: <CAHmME9poNzHS7aRdHrdaRiwy4wn7T76iL8x=qKNkT5CUEPFfYQ@mail.gmail.com> (raw)
In-Reply-To: <52D029F9.40805@xinu.at>

On Fri, Jan 10, 2014 at 6:12 PM, Florian Pritz <bluewind at xinu.at> wrote:
>
> Isn't this (fast scripting with lots of features) when people normally
> start using lua?
>

This would have the same challenges as using .so files, w.r.t. hooking
write() (or the html functions), but would be very interesting indeed,
because Lua...

Any implementation of this would probably have to work in the same way
I was thinking for the .so file. Namely, the lua script implements
event handlers for:

- filter_open(int stdout_fd, char *argv[])
- filter_write(char *data, size_t len)
- filter_close()

This seems doable. I don't know how I feel about the added size of
doing this yet, but it is enticing enough to entertain and see how the
idea develops.


  parent reply	other threads:[~2014-01-10 17:57 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-09 21:34 Jason
2014-01-09 22:29 ` mailings
2014-01-09 22:58 ` john
2014-01-10  1:41   ` Jason
2014-01-10  2:11     ` Jason
2014-01-10  4:26       ` Jason
2014-01-10  9:06       ` john
2014-01-10 15:57         ` Jason
2014-01-10 17:12           ` bluewind
2014-01-10 17:20             ` john
2014-01-10 17:43               ` mricon
2014-01-10 18:00                 ` Jason
2014-01-10 18:00               ` Jason
2014-01-10 17:57             ` Jason [this message]
2014-01-10 20:03               ` bluewind
2014-01-10 20:11                 ` john
2014-01-10 20:25                   ` bluewind
2014-01-10 20:36                     ` john
2014-01-10 20:56                       ` bluewind
2014-01-11  2:37                         ` Jason
2014-01-11  2:34                 ` Jason

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='CAHmME9poNzHS7aRdHrdaRiwy4wn7T76iL8x=qKNkT5CUEPFfYQ@mail.gmail.com' \
    --to=cgit@lists.zx2c4.com \
    /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).