char Decrypt(int a, int b)
{
  char intString[2]; //Just using this to put 'a' and 'b' together.
 
  sprintf(intString,"%d%d",a,b); //Put the integer together

x = x+33; //Undo the bias of -33

  for (ch = '!'; ch < 127; ch++) //Just keep incrementing ch until the char
    {                            //matches the ascii value in 'x'
      if (ch == x)
        return ch;
    }
  return ch;

return ((char) (x+33));

char ch;

for (ch = 'A'; ch <= 'Z'; ch++)
    printf("%d:%c\n", ch,ch);

/* demo of how to get in trouble in ways that may not
 * show up in test programs
 * Davekw7x  March, 2004
 */


#include <stdio.h>
#include <string.h>
int main()
{
  void Decrypt(int a, int b);
  char is[100];

  sprintf(is, "%d%d", 'a', 'b');
  printf("Main: strlen(is)  = %d\n", strlen(is));
  printf("Main: is          = <%s>\n", is);

  Decrypt('a', 'b');
  return 0;
}
void Decrypt(int a, int b)
{
  char intString[3]; //Just using this to put 'a' and 'b' together.
  int length;
 
  sprintf(intString,"%d%d",a,b); //Put the integer together
  length = strlen(intString);
  printf("Decrypt: length   = %d\n", length);
  printf("Decrypt: inString = <%s>\n", intString);
  /* Note: two two-digit integers written by sprintf result in
   * a total of five characters written to the array (four
   * digits plus the terminating '\0'
   * (!)
   *
   * Now, on my Windows machine with Borland BCC 5.5.1 and gnu
   * gcc 3.3.1, it seems to work ok, in this simple case, even
   * though it is writing into unknown territory (more bytes 
   * written to intString[] than were allocated).
   *
   * This results in "buffer overflow" conditions that can
   * be very dangerous.
   */
}