Page history
Talk:Huffman coding
31 October 2021
16 May 2019
10 January 2017
26 July 2014
15 July 2014
27 December 2011
26 December 2011
rosettacode>Ledrug
→Complaint about C++ example
+330
rosettacode>Spoon!
→Complaint about C++ example
m+6
rosettacode>Spoon!
→Complaint about C++ example: new section
+2,113
6 February 2010
27 March 2009
rosettacode>ShinTakezou
→The C code uses a GCC extension
+72
rosettacode>Paddy3118
→IS This OK?: Whoops
m+2
rosettacode>Paddy3118
→IS This OK?: Signed original entry.
m+60
71.106.173.110
→IS This OK?
+110
Ce
→The C code uses a GCC extension: new section
+283
rosettacode>ShinTakezou
→Category: new section
+287
26 March 2009
rosettacode>ShinTakezou
→IS This OK?
+377
rosettacode>Paddy3118
→IS This OK?: Change sort order, larger example
+408
rosettacode>Paddy3118
→IS This OK?
+2,030
76.167.241.45
no edit summary
+1,157
rosettacode>ShinTakezou
→By hand: what's wrong
m+135
rosettacode>ShinTakezou
static huff enc
+927
rosettacode>Mwn3d
Huffman coding isn't for sets of symbols with the same frequency
+285
Ce
made formulation more clear
m+7
Ce
Explanation of huffman coding
+1,552
rosettacode>Mwn3d
No it is
+347
rosettacode>Paddy3118
Concur
+169
76.167.241.45
New page: Umm... this is all wrong. Read the Wikipedia article. According to your scheme Huffman codewords would all be of the form 111...10 or 111...1, but that is not at all the case. --~~~~
+258