Talk:Caesar cipher: Difference between revisions
Caesar cipher - undiscussed deletion June 13 2016
m (signed) |
(Caesar cipher - undiscussed deletion June 13 2016) |
||
Line 11:
::::: Probably 16 bit wide characters and byte addressing? --[[User:Rdm|Rdm]] 11:19, 19 September 2011 (UTC)
:::::: Number one, the characters were eventually shaved off: I was using a 3-letter variable name instead of one char! :P Two, the line ''t:=&s'' retrieves a memory address of the string and stores it in ''t''. The code ''*t'' retrieves a byte (actually, a character-wide number) at ''t''. To advance through the string, we must increment t. I was using it on a Unicode build, so 16 bits. On an ANSI build, we could probably remove <code>,t+=2</code> and use <code>While *t++</code> or the like. (Although, incrementing in the while would screw up the use of *t in the Chr() statement.) I will add a note that the golfed version works on Unicode. --[[User:Crazyfirex|Crazyfirex]] 22:09, 19 September 2011 (UTC)
==Undiscussed deletion (JavaScript) June 13 2016==
:I notice that a functional JavaScript example was deleted without discussion on June 13 2016, and replaced only by an imperative example.
:Addition is generally preferable to deletion, particularly where approaches diverge, but more importantly, proposed deletions do need to be motivated and explained here on the discussion page.
:Unless there are objections, I propose to restore the functional version, so that readers are allowed see both approaches [[User:Hout|Hout]] ([[User talk:Hout|talk]]) 12:11, 4 November 2016 (UTC)
| |||