Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.os.linux.advocacy > #352013

Re: A maybe interesting code challenge

Path csiph.com!xmission!news.alt.net!not-for-mail
From owl <owl@rooftop.invalid>
Newsgroups comp.os.linux.advocacy
Subject Re: A maybe interesting code challenge
Date Tue, 26 Apr 2016 19:04:05 +0000 (UTC)
Organization O.W.L.
Lines 392
Message-ID <tuigo0af3@rooftop.invalid> (permalink)
References <nf87hq$ndh$1@dont-email.me> <nfd4pn$lmi$1@dont-email.me> <nfdark$dld$1@dont-email.me> <nfesbh$hsk$1@dont-email.me> <nfessd$j35$1@dont-email.me> <ghjd03af.h8h@rooftop.invalid> <nfo5ql$d1o$1@dont-email.me>
NNTP-Posting-Host boom.rooftop.invalid
User-Agent tin/2.2.1-20140504 ("Tober an Righ") (UNIX) (Linux/3.16.0-4-amd64 (x86_64))
Xref csiph.com comp.os.linux.advocacy:352013

Show key headers only | View raw


DFS <nospam@dfs.com> wrote:
> On 4/23/2016 1:59 AM, owl wrote:
>> DFS <nospam@dfs.com> wrote:
>>> On 4/23/2016 12:09 AM, Norman Peelman wrote:
>>>
>>>>     So, (curiosity) what is wrong with it?
>>>
>>>
>>> A bunch of stuff I didn't want to track down and fix.
>>>
>>> VBScript has some significant differences from VB/A.
>>>
>>> If you develop and test under VBScript you'll see.
>>>
>>>
>>>
>>>> Anyway, you do understand
>>>> that you are doing unnecessary work by having:
>>>>
>>>> criteria >= 1  -- every time criteria is 1,2 or 3 these lines run
>>>> criteria >= 2  -- every time criteria is 2 or 3 these lines run
>>>
>>>
>>> Yes, I recognized that immediately after I posted it.  The fix shaved
>>> 0.014 seconds off run time.
>>>
>>
>> Your gonna hate me.  I figured the 2.7 sec was low for a C app.
>> I went over the code and removed some stupid shit and now baby's
>> on fire.  The first one, "input_e", is the 6000 line input file
>> that gave me the 2.7 sec.  Now it's 0.048 sec.  :)  And a 600k
>> line file gets burned up in 1.376 sec, generating 3.6 million
>> lines of output.
> 
> Nice.  Code or it didn't happen :)
> 

Below.

> You're not actually writing 3.6M lines to a file, right?
> 
 

Yes.  I have since made some modifications to the code, so that it
handles an an arbirary number of input lines and allocates memory
based on file size.  Before it was hardcoded in arrays of fixed size.
(Still uses fixed max ending line length estimate of 128 bytes at this
point, as well as fixed field count of 6 based on initial count of ';',
so it's not completely robust yet).

This resulted in a speed decrease to about 2-3 sec IIRC for writing a 3.6
million line file.  Right now I have 8 instances of that md5/ip cracking
thing running, and times are way, off so I can't show a realistic
measure.

I didn't use the regex.h stuff -- just walked the file and did
byte comparisons.  I figured added function calls with regex
would be slower, but I might try it that way later and see what
happens.

----------------------- begin code ------------------------

#include <stdio.h>
#include <stdlib.h>
#include <string.h>

#define LINELENGTH 128

struct vars{
  char field1[LINELENGTH];
  char value1[LINELENGTH];
  char field2[LINELENGTH];
  char value2[LINELENGTH];
  char field3[LINELENGTH];
  char value3[LINELENGTH];
};


int main(int argc, char *argv[])
{
  int c=0;
  int i=0;
  int j=0;
  int k=0;
  long filesize=0;  

  FILE *fp=NULL;
  int newlinecount=0;
  int semicount=0;

  struct vars *varsarr;

  const char s[2]=";";
  char *token;

  char *sourcebuffer;
  char *targetbuffer;
  char *tempbuffer;

  if ( argc != 2 )
  {
   fprintf(stderr,"need a filename\n");
   exit(1);
  }

  char *inputfilename = argv[1];
  if( (fp=fopen(inputfilename,"r")) == NULL )
  {
    fprintf(stderr,"no file\n");
    exit(1);
  }
  fseek(fp,0,SEEK_END); 
  filesize=ftell(fp);
  fseek(fp,0,SEEK_SET);

  sourcebuffer = malloc(2 * filesize  +1 ); 
  if (sourcebuffer==NULL)
  {
    fprintf(stderr,"sourcebuffer malloc()\n");
    exit(1);
  }

  targetbuffer = malloc(2 * filesize  +1 ); 
  if (targetbuffer==NULL)
  {
    fprintf(stderr,"targetbuffer malloc()\n");
    exit(1);
  }

  while( (c=fgetc(fp))!= EOF )
  {
    if ( c == '\n' )
    {
       targetbuffer[i]=c;
       newlinecount++;
    }
    if ( c == ' ' )
    {
     targetbuffer[i++]=c;
      c=fgetc(fp); 
      if ( c == 'l' )
      {
        c=fgetc(fp); 
        if ( c == 'i' )
        {
           c=fgetc(fp);
           if( c == 'k' )
           {
              c=fgetc(fp);
              if( c == 'e' )
              {
                c=fgetc(fp);
                if ( c == ' ' )
                {
                  targetbuffer[i++]='='; 
                }
                else /* c != ' ' */
                {
                  targetbuffer[i++]=c;  
                }
              }
              else /* c != 'e' */
              {
                 targetbuffer[i++]=c;
              }
           }
           else /* c != 'k' */
           {
             targetbuffer[i++]=c;
           }
        }    
        else /* c != 'i' */
        {
          targetbuffer[i++]=c;
        }
      }
      else /* c != 'l' */
      {
        targetbuffer[i++]=c;
      }
    } 
    else /* c != ' ' */
    {
      targetbuffer[i++]=c;
    }
  } /* while loop */

  for (i=0;targetbuffer[i]!='\0';i++)
  {
    c=targetbuffer[i];
    if(c=='=')
    {
      targetbuffer[i]=';';
    }
  }

  tempbuffer=sourcebuffer; /* c=a */
  sourcebuffer=targetbuffer; /* a=b */
  targetbuffer=tempbuffer;  /* b=c */
 
  for (i=0,j=0;sourcebuffer[i]!='\0';i++,j++)
  {
    c=sourcebuffer[i];
    targetbuffer[j]=c;
    if(c==';')
    {
      semicount++;
    }
    if (c=='\n')
    {
      if (semicount < 6)
      {
        for(k=semicount;k<6;k++)
        {
           targetbuffer[j++]=';';
        }      
      }
      semicount=0;
      targetbuffer[j]=c;
    }
  }

  tempbuffer=sourcebuffer; /* c=a */
  sourcebuffer=targetbuffer; /* a=b */
  targetbuffer=tempbuffer;  /* b=c */
 
  for (i=0,j=0;sourcebuffer[i]!='\0';i++,j++)
  {
    if(sourcebuffer[i]==' ')
    {
       if(sourcebuffer[i+1]==';')
       {
         targetbuffer[j]=sourcebuffer[i+1]; 
         i++;
       } 
       else
       {
         targetbuffer[j]=sourcebuffer[i]; 
       }
    }
    else
    {
      targetbuffer[j]=sourcebuffer[i];
    }
  }

  tempbuffer=sourcebuffer; /* c=a */
  sourcebuffer=targetbuffer; /* a=b */
  targetbuffer=tempbuffer;  /* b=c */

  for (i=0,j=0;sourcebuffer[i]!='\0';i++,j++)
  {
    if(sourcebuffer[i]==';')
    {
       targetbuffer[j]=sourcebuffer[i]; 
  
       if(sourcebuffer[i+1]==' ')
       {
         i++;
       } 
    }
    else
    {
      targetbuffer[j]=sourcebuffer[i];
    }
  }
  targetbuffer[j]='\0';

  tempbuffer=sourcebuffer; /* c=a */
  sourcebuffer=targetbuffer; /* a=b */
  targetbuffer=tempbuffer;  /* b=c */

  for (i=0,j=0;sourcebuffer[i]!='\0';i++,j++)
  {
    if(sourcebuffer[i]=='\n')
    {
      i++;
      targetbuffer[j]=sourcebuffer[i];
    }
    else
    {
      targetbuffer[j]=sourcebuffer[i];
    }
  }
  targetbuffer[j]='\0';

  tempbuffer=sourcebuffer; /* c=a */
  sourcebuffer=targetbuffer; /* a=b */
  targetbuffer=tempbuffer;  /* b=c */

  semicount=0;
  targetbuffer[0]='\'';
  for (i=0,j=1;sourcebuffer[i]!='\0';i++,j++)
  {
    if(sourcebuffer[i]==';')
    {
      semicount++;
      targetbuffer[j]='\'';
      targetbuffer[++j]=sourcebuffer[i];
      targetbuffer[++j]='\'';
    }
    else
    {
       targetbuffer[j]=sourcebuffer[i];
    }
  }
  targetbuffer[--j]='\0';

  tempbuffer=sourcebuffer; /* c=a */
  sourcebuffer=targetbuffer; /* a=b */
  targetbuffer=tempbuffer;  /* b=c */
  
  varsarr=malloc( newlinecount * sizeof(*varsarr));

  if (varsarr==NULL)
  {
    fprintf(stderr,"varsarr malloc()\n");
    exit(1);
  }

  token=strtok(sourcebuffer,s);
  for (i=0;i<newlinecount*6;i++)
  {
     if(token==NULL)
     {
        break;
     }
     if (!strcmp(token,"\n"))
     {
       break;
     }
     strcat(varsarr[i].field1,token);     
     printf("var field1 = %s\n",varsarr[i].field1);

     token=strtok(NULL,s);

     if(token==NULL)
     {
        break;
     }
     strcat(varsarr[i].value1,token);     
     printf("var value1 = %s\n",varsarr[i].value1);

     token=strtok(NULL,s);

     if(token==NULL)
     {
        break;
     }
     strcat(varsarr[i].field2,token);     
     printf("var field2 = %s\n",varsarr[i].field2);

     token=strtok(NULL,s);

     if(token==NULL)
     {
        break;
     }
     strcat(varsarr[i].value2,token);     
     printf("var value2 = %s\n",varsarr[i].value2);

     token=strtok(NULL,s);

     if(token==NULL)
     {
        break;
     }
     strcat(varsarr[i].field3,token);     
     printf("var field3 = %s\n",varsarr[i].field3);

     token=strtok(NULL,s);

     if(token==NULL)
     {
        break;
     }
     strcat(varsarr[i].value3,token);     
     printf("var value3 = %s\n",varsarr[i].value3);

     token=strtok(NULL,s);
  }

  free(sourcebuffer);
  free(targetbuffer);
  free(varsarr);

  fclose(fp);

  return 0; 
}

------------------------ end code -------------------------

Back to comp.os.linux.advocacy | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

A maybe interesting code challenge DFS <nospam@dfs.com> - 2016-04-20 11:37 -0400
  Re: A maybe interesting code challenge Steve Carroll <fretwizzer@gmail.com> - 2016-04-20 08:45 -0700
    Re: A maybe interesting code challenge DFS <nospam@dfs.com> - 2016-04-20 11:57 -0400
      Re: A maybe interesting code challenge Steve Carroll <fretwizzer@gmail.com> - 2016-04-20 09:02 -0700
      Re: A maybe interesting code challenge owl <owl@rooftop.invalid> - 2016-04-21 01:54 +0000
        Re: A maybe interesting code challenge Steve Carroll <fretwizzen@gmail.com> - 2016-04-20 18:57 -0700
        Re: A maybe interesting code challenge owl <owl@rooftop.invalid> - 2016-04-21 02:45 +0000
          Re: A maybe interesting code challenge DFS <nospam@dfs.com> - 2016-04-20 23:01 -0400
            Re: A maybe interesting code challenge owl <owl@rooftop.invalid> - 2016-04-21 03:56 +0000
              Re: A maybe interesting code challenge DFS <nospam@dfs.com> - 2016-04-21 11:06 -0400
                Re: A maybe interesting code challenge owl <owl@rooftop.invalid> - 2016-04-21 16:13 +0000
                Re: A maybe interesting code challenge DFS <nospam@dfs.com> - 2016-04-21 17:27 -0400
                Re: A maybe interesting code challenge owl <owl@rooftop.invalid> - 2016-04-22 19:07 +0000
  Re: A maybe interesting code challenge Steve Carroll <fretwizzen@gmail.com> - 2016-04-20 19:01 -0700
  Re: A maybe interesting code challenge Fabian Russell <fb@zen.info> - 2016-04-22 09:37 +0000
    Re: A maybe interesting code challenge Norman Peelman <npeelman@cfl.rr.com> - 2016-04-22 08:33 -0400
      Re: A maybe interesting code challenge Fabian Russell <fb@zen.info> - 2016-04-22 22:03 +0000
        Re: A maybe interesting code challenge Richard King <kingsley651@webby.org> - 2016-04-22 18:22 -0400
    Re: A maybe interesting code challenge owl <owl@rooftop.invalid> - 2016-04-22 19:48 +0000
      Re: A maybe interesting code challenge DFS <nospam@dfs.com> - 2016-04-22 17:24 -0400
        Re: A maybe interesting code challenge owl <owl@rooftop.invalid> - 2016-04-22 22:18 +0000
          Re: A maybe interesting code challenge Fabian Russell <fb@zen.info> - 2016-04-22 22:26 +0000
            Re: A maybe interesting code challenge owl <owl@rooftop.invalid> - 2016-04-22 22:43 +0000
              Re: A maybe interesting code challenge Fabian Russell <fb@zen.info> - 2016-04-22 22:50 +0000
                Re: A maybe interesting code challenge owl <owl@rooftop.invalid> - 2016-04-22 22:57 +0000
                Re: A maybe interesting code challenge Fabian Russell <fb@zen.info> - 2016-04-23 13:07 +0000
                Re: A maybe interesting code challenge Norman Peelman <npeelman@cfl.rr.com> - 2016-04-23 09:58 -0400
      Re: A maybe interesting code challenge Fabian Russell <fb@zen.info> - 2016-04-22 21:48 +0000
    Re: A maybe interesting code challenge DFS <nospam@dfs.com> - 2016-04-22 17:00 -0400
      Re: A maybe interesting code challenge Fabian Russell <fb@zen.info> - 2016-04-22 21:56 +0000
        Re: A maybe interesting code challenge DFS <nospam@dfs.com> - 2016-04-22 19:39 -0400
          Re: A maybe interesting code challenge Fabian Russell <fb@zen.info> - 2016-04-23 15:25 +0000
            Re: A maybe interesting code challenge DFS <nospam@dfs.com> - 2016-04-23 13:14 -0400
              Re: A maybe interesting code challenge owl <owl@rooftop.invalid> - 2016-04-23 18:37 +0000
                Re: A maybe interesting code challenge DFS <nospam@dfs.com> - 2016-04-23 16:50 -0400
                Re: A maybe interesting code challenge owl <owl@rooftop.invalid> - 2016-04-23 21:15 +0000
                Re: A maybe interesting code challenge DFS <nospam@dfs.com> - 2016-04-23 18:36 -0400
                Re: A maybe interesting code challenge owl <owl@rooftop.invalid> - 2016-04-23 23:24 +0000
  Re: A maybe interesting code challenge Norman Peelman <npeelman@cfl.rr.com> - 2016-04-22 08:21 -0400
    Re: A maybe interesting code challenge DFS <nospam@dfs.com> - 2016-04-22 10:04 -0400
      Re: A maybe interesting code challenge Norman Peelman <npeelman@cfl.rr.com> - 2016-04-23 00:09 -0400
        Re: A maybe interesting code challenge DFS <nospam@dfs.com> - 2016-04-23 00:18 -0400
          Re: A maybe interesting code challenge owl <owl@rooftop.invalid> - 2016-04-23 05:59 +0000
            Re: A maybe interesting code challenge DFS <nospam@dfs.com> - 2016-04-26 12:46 -0400
              Re: A maybe interesting code challenge owl <owl@rooftop.invalid> - 2016-04-26 19:04 +0000
                Re: A maybe interesting code challenge owl <owl@rooftop.invalid> - 2016-04-26 20:40 +0000
                Re: A maybe interesting code challenge DFS <nospam@dfs.com> - 2016-04-26 17:48 -0400
                Re: A maybe interesting code challenge owl <owl@rooftop.invalid> - 2016-04-26 22:14 +0000
          Re: A maybe interesting code challenge Norman Peelman <npeelman@cfl.rr.com> - 2016-04-23 23:15 -0400
            Re: A maybe interesting code challenge DFS <nospam@dfs.com> - 2016-04-23 23:30 -0400
              Re: A maybe interesting code challenge Norman Peelman <npeelman@cfl.rr.com> - 2016-04-24 08:52 -0400
                Re: A maybe interesting code challenge Chris Ahlstrom <OFeem1987@teleworm.us> - 2016-04-24 10:06 -0400
                Re: A maybe interesting code challenge Fabian Russell <fb@zen.info> - 2016-04-24 15:59 +0000
              Re: A maybe interesting code challenge Norman Peelman <npeelman@cfl.rr.com> - 2016-04-24 15:45 -0400
                Re: A maybe interesting code challenge DFS <nospam@dfs.com> - 2016-04-25 10:19 -0400
                Re: A maybe interesting code challenge Norman Peelman <npeelman@cfl.rr.com> - 2016-04-25 20:26 -0400
                Re: A maybe interesting code challenge DFS <nospam@dfs.com> - 2016-04-25 23:24 -0400
                Re: A maybe interesting code challenge owl <owl@rooftop.invalid> - 2016-04-26 05:03 +0000
                Re: A maybe interesting code challenge DFS <nospam@dfs.com> - 2016-04-26 11:40 -0400
  Re: A maybe interesting code challenge Sandman <mr@sandman.net> - 2016-04-25 15:14 +0000
    Re: A maybe interesting code challenge DFS <nospam@dfs.com> - 2016-04-25 12:05 -0400
      Re: A maybe interesting code challenge Sandman <mr@sandman.net> - 2016-04-25 18:06 +0000
        Re: A maybe interesting code challenge DFS <nospam@dfs.com> - 2016-04-26 12:41 -0400
          Re: A maybe interesting code challenge Sandman <mr@sandman.net> - 2016-04-26 18:03 +0000
            Re: A maybe interesting code challenge DFS <nospam@dfs.com> - 2016-04-26 17:39 -0400
              Re: A maybe interesting code challenge Sandman <mr@sandman.net> - 2016-04-27 05:50 +0000
                Re: A maybe interesting code challenge chrisv <chrisv@nospam.invalid> - 2016-04-27 06:43 -0500
                Re: A maybe interesting code challenge William Poaster <wp@dev.null> - 2016-04-27 13:11 +0100
                Re: A maybe interesting code challenge Sandman <mr@sandman.net> - 2016-04-27 13:32 +0000
                Re: A maybe interesting code challenge Steve Carroll <fretwizzer@gmail.com> - 2016-04-27 07:32 -0700
                Re: A maybe interesting code challenge Sandman <mr@sandman.net> - 2016-04-27 15:02 +0000
                Re: A maybe interesting code challenge Steve Carroll <fretwizzer@gmail.com> - 2016-04-27 08:17 -0700
                Re: A maybe interesting code challenge Sandman <mr@sandman.net> - 2016-04-27 16:21 +0000
                Re: A maybe interesting code challenge Steve Carroll <fretwizzer@gmail.com> - 2016-04-27 09:42 -0700
                Re: A maybe interesting code challenge Sandman <mr@sandman.net> - 2016-04-27 21:39 +0000
                Re: A maybe interesting code challenge owl <owl@rooftop.invalid> - 2016-04-27 23:25 +0000
                Re: A maybe interesting code challenge Sandman <mr@sandman.net> - 2016-04-28 05:34 +0000
                Re: A maybe interesting code challenge vallor <vallor@cultnix.org> - 2016-04-28 05:37 +0000
                Re: A maybe interesting code challenge Sandman <mr@sandman.net> - 2016-04-28 05:42 +0000
                Re: A maybe interesting code challenge DFS <nospam@dfs.com> - 2016-04-27 11:45 -0400
                Re: A maybe interesting code challenge Sandman <mr@sandman.net> - 2016-04-27 16:23 +0000
                Re: A maybe interesting code challenge Peter Köhlmann <peter-koehlmann@t-online.de> - 2016-04-27 18:40 +0200
                Re: A maybe interesting code challenge Steve Carroll <fretwizzer@gmail.com> - 2016-04-27 09:58 -0700
                Re: A maybe interesting code challenge Peter Köhlmann <peter-koehlmann@t-online.de> - 2016-04-27 20:57 +0200
                Re: A maybe interesting code challenge Steve Carroll <fretwizzer@gmail.com> - 2016-04-27 12:06 -0700
                Re: A maybe interesting code challenge Peter Köhlmann <peter-koehlmann@t-online.de> - 2016-04-27 22:44 +0200
                Re: A maybe interesting code challenge DFS <nospam@dfs.com> - 2016-04-27 13:38 -0400
                Re: A maybe interesting code challenge Steve Carroll <fretwizzer@gmail.com> - 2016-04-27 11:07 -0700
                Re: A maybe interesting code challenge DFS <nospam@dfs.com> - 2016-04-27 15:51 -0400
                Re: A maybe interesting code challenge Steve Carroll <fretwizzer@gmail.com> - 2016-04-27 13:30 -0700
                Re: A maybe interesting code challenge Norman Peelman <npeelman@cfl.rr.com> - 2016-04-27 21:38 -0400
                Re: A maybe interesting code challenge DFS <nospam@dfs.com> - 2016-04-28 11:33 -0400
                Re: A maybe interesting code challenge Steve Carroll <fretwizzer@gmail.com> - 2016-04-28 09:14 -0700
                Re: A maybe interesting code challenge DFS <nospam@dfs.com> - 2016-04-28 14:17 -0400
                Re: A maybe interesting code challenge Sandman <mr@sandman.net> - 2016-04-28 18:49 +0000
                Re: A maybe interesting code challenge Steve Carroll <fretwizzer@gmail.com> - 2016-04-29 08:42 -0700
                Re: A maybe interesting code challenge DFS <nospam@dfs.com> - 2016-04-29 13:42 -0400
                Re: A maybe interesting code challenge Snit <usenet@gallopinginsanity.com> - 2016-04-29 10:54 -0700
                Re: A maybe interesting code challenge Steve Carroll <fretwizzer@gmail.com> - 2016-04-29 11:20 -0700
                Re: Snit digest 214 / 2016-04-29 Melzzzzz <mel@zzzzz.com> - 2016-04-30 00:31 +0200
                Re: Snit digest 214 / 2016-04-29 DFS <nospam@dfs.com> - 2016-04-29 19:00 -0400
                Re: Snit digest 214 / 2016-04-29 DFS <nospam@dfs.com> - 2016-04-30 10:36 -0400
                Re: Snit digest 214 / 2016-04-29 chrisv <chrisv@nospam.invalid> - 2016-05-02 07:54 -0500
                Re: Snit digest 214 / 2016-04-29 Peter Köhlmann <peter-koehlmann@t-online.de> - 2016-05-02 15:55 +0200
                Re: Snit digest 214 / 2016-04-29 Snit <usenet@gallopinginsanity.com> - 2016-05-02 07:23 -0700
                Snit digest 215 / 2016-05-02 Sandman <mr@sandman.net> - 2016-05-02 14:39 +0000
                Re: Snit digest 215 / 2016-05-02 Snit <usenet@gallopinginsanity.com> - 2016-05-02 07:54 -0700
                Re: Snit digest 214 / 2016-04-29 Sandman <mr@sandman.net> - 2016-05-02 14:36 +0000
                Re: Snit digest 214 / 2016-04-29 Snit <usenet@gallopinginsanity.com> - 2016-05-02 07:53 -0700
                Re: A maybe interesting code challenge Steve Carroll <fretwizzer@gmail.com> - 2016-04-29 11:11 -0700
                Re: A maybe interesting code challenge Steve Carroll <fretwizzer@gmail.com> - 2016-04-29 14:44 -0700
                Re: A maybe interesting code challenge DFS <nospam@dfs.com> - 2016-04-29 17:53 -0400
                Re: A maybe interesting code challenge Melzzzzz <mel@zzzzz.com> - 2016-04-29 23:56 +0200
                Re: A maybe interesting code challenge DFS <nospam@dfs.com> - 2016-04-29 18:09 -0400
                Re: A maybe interesting code challenge Chris Ahlstrom <OFeem1987@teleworm.us> - 2016-04-29 19:09 -0400
                Re: A maybe interesting code challenge Steve Carroll <fretwizzer@gmail.com> - 2016-04-30 07:31 -0700
                Re: A maybe interesting code challenge Sandman <mr@sandman.net> - 2016-05-01 08:21 +0000
                Re: A maybe interesting code challenge Steve Carroll <fretwizzer@gmail.com> - 2016-05-01 08:47 -0700
                Re: A maybe interesting code challenge DFS <nospam@dfs.com> - 2016-05-02 14:54 -0400
                Re: A maybe interesting code challenge DFS <nospam@dfs.com> - 2016-05-02 21:54 -0400
                Re: A maybe interesting code challenge GreyCloud <mist@cumulus.com> - 2016-04-28 15:39 -0600
                Re: A maybe interesting code challenge Steve Carroll <fretwizzer@gmail.com> - 2016-04-29 08:48 -0700
                Re: A maybe interesting code challenge GreyCloud <mist@cumulus.com> - 2016-04-29 16:57 -0600
                Re: A maybe interesting code challenge Norman Peelman <npeelman@cfl.rr.com> - 2016-04-27 21:33 -0400
                Re: A maybe interesting code challenge Chris Ahlstrom <OFeem1987@teleworm.us> - 2016-04-28 05:45 -0400
                Re: A maybe interesting code challenge Sandman <mr@sandman.net> - 2016-04-27 21:32 +0000
                Re: A maybe interesting code challenge Norman Peelman <npeelman@cfl.rr.com> - 2016-04-27 21:48 -0400
                Re: A maybe interesting code challenge DFS <nospam@dfs.com> - 2016-04-27 22:57 -0400
                Re: A maybe interesting code challenge Sandman <mr@sandman.net> - 2016-04-28 05:44 +0000
                Re: A maybe interesting code challenge DFS <nospam@dfs.com> - 2016-04-29 16:32 -0400
                Re: A maybe interesting code challenge DFS <nospam@dfs.com> - 2016-04-27 23:05 -0400
                Re: A maybe interesting code challenge owl <owl@rooftop.invalid> - 2016-04-28 03:20 +0000
                Re: A maybe interesting code challenge DFS <nospam@dfs.com> - 2016-04-28 09:52 -0400
                Re: A maybe interesting code challenge Norman Peelman <npeelman@cfl.rr.com> - 2016-04-29 02:46 -0400
                Re: A maybe interesting code challenge Steve Carroll <fretwizzer@gmail.com> - 2016-04-29 08:33 -0700
                Re: A maybe interesting code challenge Norman Peelman <npeelman@cfl.rr.com> - 2016-04-30 09:31 -0400
                Re: A maybe interesting code challenge Sandman <mr@sandman.net> - 2016-04-28 05:42 +0000
                Re: A maybe interesting code challenge vallor <vallor@cultnix.org> - 2016-04-28 06:17 +0000
                Re: A maybe interesting code challenge Sandman <mr@sandman.net> - 2016-04-28 06:56 +0000
                Re: A maybe interesting code challenge Chris Ahlstrom <OFeem1987@teleworm.us> - 2016-04-28 05:46 -0400

csiph-web