Talk:UUencode (C)

From LiteratePrograms
Jump to: navigation, search

[edit] Table permission

I got permission from User:Greycat on the English Wikipedia to use this nice table here. Since we don't have the wikitable class I've added a bit of markup to make it look the same as on WP.

[edit] Sample uuencode table license

Hi there. I noticed this beautifully illustrative table you added to the uuencode article:

Original characters C a t
Original ASCII, decimal 67 97 116
ASCII, binary 0 1 0 0 0 0 1 1 0 1 1 0 0 0 0 1 0 1 1 1 0 1 0 0
New decimal values 16 54 5 52
+32 48 86 37 84
Uuencoded characters 0 V % T

This evidently involved a fair amount of effort. I have a page on another wiki which discusses an implementation of uuencode which this table would be very useful in illustrating, but the license on this wiki does not permit GFDL material. Could I persuade you to release your table under either the MIT license or public domain, and to similarly release your license statement for posting there? Thanks. Deco 02:51, 7 September 2006 (UTC)

Sure, no problem. Shall I write something somewhere or just writing here that this table is explicitly released in public domain will do? --GreyCat 06:43, 7 September 2006 (UTC)
That's good, thanks a lot. :-) Deco 06:44, 7 September 2006 (UTC)
That sure is a nice table. I wanted to use it in the article, but was afraid of the licensing issues.
Why isn't class="wikitable" available in this wiki? It would make it really easy to create nice-looking tables. Ahy1 09:35, 8 September 2006 (PDT)

[edit] Shift operator and noweb

I see the LSHIFT() macro is removed and the order of the shift sub-expressions are reversed. I think that was tried in Hash function comparison (C, sh) without really solving the problem. Noweb still got confused by the shift operators, when generating the code.

My noweave/notangle man-page states that we can use "@<<" for a literal "<<", but that doesn't seem to work here (in preview). It would also make the code look strange. Maybe a special code, where we state that we really want "<<", should be introduced in <codeblock>s. This would probably involve some regex-processing before and after it is processed by noweb. I don't know how much work this would be or if it is at all possible, but this problem will probably show up in most articles doing shift operations in C and other languages with C-like syntax. Ahy1 09:58, 8 September 2006 (PDT)

It didn't occur to me how commonly this sequence would arise in practice. It appears that in actuality, the "@<<" code does work correctly (in the downloaded file); it is the codeblock regex for identifying noweb chunks for the purpose of syntax highlighting and removing the surrounding brackets that is incorrect. I'll fix this at once. We don't have wikitable just because it's part of the custom on-wiki CSS at WP, which first of all I haven't set up and second is licensed under the GFDL (I might make it part of the general exception for interface elements, I don't know). Deco 11:14, 8 September 2006 (PDT)
I've now fixed the "@<<" sequence to work correctly. It is rendered as an ordinary "<<" when the codeblock is rendered, and is not turned into a boxed link. It's still the wrong colour, but I think that's okay. The downloaded file and download code preview are also correct now. Deco 12:28, 8 September 2006 (PDT)
Yes, of course it was only the rendering. I should have tested it properly before claiming it doesn't work. The wrong color is not a big issue. I don't think most people will notice the difference.
The wikitable thing isn't that important. Ahy1 15:11, 8 September 2006 (PDT)