Talk:Run-length encoding: Difference between revisions
Content added Content deleted
(task is too limited (can't encode digits)) |
(alternate encoding) |
||
Line 1: | Line 1: | ||
"The output can be anything." might be too open-ended. I would prefer it if all the solutions did it the same way, or something. --[[Special:Contributions/76.167.241.45|76.167.241.45]] 18:32, 24 April 2009 (UTC) |
"The output can be anything." might be too open-ended. I would prefer it if all the solutions did it the same way, or something. --[[Special:Contributions/76.167.241.45|76.167.241.45]] 18:32, 24 April 2009 (UTC) |
||
I would prefer this task to use a run length encoding which will work at least on all ASCII characters. The current encoding can't represent [0-9]. --[[User:IanOsgood|IanOsgood]] 19:27, 24 April 2009 (UTC) |
I would prefer this task to use a run length encoding which will work at least on all ASCII characters. The current encoding can't represent [0-9]. A more flexible encoding is implemented [http://wiki.forthfreak.net/index.cgi?RunLengthEncoding here]. --[[User:IanOsgood|IanOsgood]] 19:27, 24 April 2009 (UTC) |
||
* Run code has high bit set, remaining 7 bits are run length-1. |
|||
* Bytes in stream with high bit set are always encoded as a run, perhaps with a length of only one. |
Revision as of 20:39, 24 April 2009
"The output can be anything." might be too open-ended. I would prefer it if all the solutions did it the same way, or something. --76.167.241.45 18:32, 24 April 2009 (UTC)
I would prefer this task to use a run length encoding which will work at least on all ASCII characters. The current encoding can't represent [0-9]. A more flexible encoding is implemented here. --IanOsgood 19:27, 24 April 2009 (UTC)
- Run code has high bit set, remaining 7 bits are run length-1.
- Bytes in stream with high bit set are always encoded as a run, perhaps with a length of only one.