Talk:Run-length encoding: Difference between revisions

no edit summary
(→‎Is built-in on topic?: not deprecated)
No edit summary
 
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)
 
I totally agree. The current description makes comparing language solutions often pointless or misleading. The encoded output should be as described in the given example in the challenge.[[User:Martinfreedman|Martinfreedman]] ([[User talk:Martinfreedman|talk]])
 
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)
Line 20 ⟶ 22:
 
This would make the task (or at least, the solution) ASCII-centric, that is, it wouldn't work for EBCDIC characters, nor ASCII-8 characters. -- [[User:Gerard Schildberger|Gerard Schildberger]] 17:01, 29 December 2012 (UTC)
 
The challenge as is, (preferably with a consistent encoded format as in the provided example), is a standard coding challenge used elsewhere. You could say it is a toy RLE rather than the real thing but it does illustrate a language's abilities in list/sequence processing of chars (and/or regex). [[User:Martinfreedman|Martinfreedman]] ([[User talk:Martinfreedman|talk]])
 
== PowerBASIC format wrong ==