mdebray/tvl-depot
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
tvl-depot/third_party/lisp/mime4cl/README.md

32 lines
1.3 KiB
Markdown
Raw Normal View History

docs(3p/lisp/mime4cl): describe changes compared to original version Spell out that “may diverge” is more of a “has diverged by now”. We are essentially maintaining a fork of mime4cl. Change-Id: I9049e8296a666c3d1b08eae28813147f360771ef Reviewed-on: https://cl.tvl.fyi/c/depot/+/8621 Autosubmit: sterni <sternenseemann@systemli.org> Reviewed-by: sterni <sternenseemann@systemli.org> Tested-by: BuildkiteCI
2023-05-19 02:55:59 +02:00
# mime4cl
`MIME4CL` is a Common Lisp library for dealing with MIME messages. It was
originally been written by Walter C. Pelissero and vendored into depot
([mime4cl-20150207T211851.tbz](http://wcp.sdf-eu.org/software/mime4cl-20150207T211851.tbz)
to be exact) as upstream has become inactive. Its [original
website](http://wcp.sdf-eu.org/software/#mime4cl) can still be accessed.
The depot version has since diverged from upstream. Main aims were to improve
performance and reduce code size by relying on third party libraries like
flexi-streams. It is planned to improve encoding handling in the long term.
docs(3p/lisp/mime4cl): add clear warning about current state I'm not really describing what the problem here is because I don't think a writeup is really useful. It would just be speculation and I don't need to syncronize my efforts with anyone at the moment, so it's best to keep those notes offline. Basically, the next problem I want to tackle is that the initial parsing of a multipart message (to get the number, types, offsets etc. of the different parts) is very slow. This is because READ-LINE on a FLEXI-STREAM dispatches to READ-CHAR which is laughably slow. Change-Id: Ia5d6e335abb23639cfe9c2149ead99ffa5dbbcf5 Reviewed-on: https://cl.tvl.fyi/c/depot/+/12936 Reviewed-by: sterni <sternenseemann@systemli.org> Autosubmit: sterni <sternenseemann@systemli.org> Tested-by: BuildkiteCI
2024-12-27 00:55:39 +01:00
Work towards this happens intermittently.
WARNING:
mime4cl currently doesn't have a _comprehensive_ test suite
and decidedly lacks performance.
docs(3p/lisp/mime4cl): describe changes compared to original version Spell out that “may diverge” is more of a “has diverged by now”. We are essentially maintaining a fork of mime4cl. Change-Id: I9049e8296a666c3d1b08eae28813147f360771ef Reviewed-on: https://cl.tvl.fyi/c/depot/+/8621 Autosubmit: sterni <sternenseemann@systemli.org> Reviewed-by: sterni <sternenseemann@systemli.org> Tested-by: BuildkiteCI
2023-05-19 02:55:59 +02:00
## Differences from the original version
chore(3p/lisp/mime4cl): drop ASDF build system Change-Id: I2d91937d48e62ae90404eead36ef3cfc790675f2 Reviewed-on: https://cl.tvl.fyi/c/depot/+/12937 Autosubmit: sterni <sternenseemann@systemli.org> Tested-by: BuildkiteCI Reviewed-by: sterni <sternenseemann@systemli.org>
2024-12-31 22:17:44 +01:00
* `//nix/buildLisp` is used as the build system. ASDF has been removed
since it was untested (it should be reintroduced once mime4cl is
“ready”).
docs(3p/lisp/mime4cl): describe changes compared to original version Spell out that “may diverge” is more of a “has diverged by now”. We are essentially maintaining a fork of mime4cl. Change-Id: I9049e8296a666c3d1b08eae28813147f360771ef Reviewed-on: https://cl.tvl.fyi/c/depot/+/8621 Autosubmit: sterni <sternenseemann@systemli.org> Reviewed-by: sterni <sternenseemann@systemli.org> Tested-by: BuildkiteCI
2023-05-19 02:55:59 +02:00
* The dependency on [sclf](http://wcp.sdf-eu.org/software/#sclf) has been
eliminated by inlining the relevant parts.
* `MY-STRING-INPUT-STREAM`, `DELIMITED-INPUT-STREAM`,
`CHARACTER-INPUT-ADAPTER-STREAM`, `BINARY-INPUT-ADAPTER-STREAM` etc. have been
replaced by (thin wrappers around) flexi-streams. In addition to improved
handling of encodings, this allows using `READ-SEQUENCE` via the gray stream
interface.
Reference in a new issue Copy permalink