Re: Spiro Japh 2

[QM]

in reply to Spiro Japh 2

Taking that a bit further...

Why have warnings on if it's not warnings clean?

Also, why not print the whole thing instead of the initials? You can probably do way better than this, but I'm just making the suggestion.

#!/usr/bin/perl                            -- unless don't
eval{     require                        Win32::Console::ANSI;
};sub      ::{printf                  @_ } sub            sub{
rand          39/999}               sub O123                 {::
""            ."\e[%d"            .";%dH%s"                  ,@_
;};               sub l234      {O123 $|=                    1
,1,                 "\e[J"}   while(1)                      {
$c                    or do {::"\e[1"                    ."".
 ""                    .";%dm", 30+                     rand
  7 ;                  l234;$u=&sub                  ;$v =
   &sub                ;$ c= 3999                 ;$b=qw
    /19 9            1/[int rand 3             ]};O123
     11*sin(      $v* $c)+    13,39*cos   ($u*$c)+41,
       qw+J u s t A n             o t h e r P e 
         r l H a c                  k e r+[$c
           %21];                     ($a++%
             $b)           or         $c--;}

[liverpole]

I'll be honest with you, I think it's better with with just the letters "JAPH" (or even "Japh"), as there's too much jibberish when you use all 4 words.  Additionally, the new picture looks worse, partly since it's -supposed- to be one of the self-generated patterns, and partly because it's just graphically not as good (eg. the dangling 'or' at the bottom looks out-of-place).

But I'll agree with you on the warnings.  What happened was that after developing it under Windows, when I tried it the first time on Linux, I didn't actually see the warnings until long after I'd published it.

[QM]

...the new picture looks worse, partly since it's -supposed- to be one of the self-generated patterns, and partly because it's just graphically not as good (eg. the dangling 'or' at the bottom looks out-of-place).

So reformat it. Seriously, I just took a quick stab at it. I don't have the patience or skills, but I admire them in others.

But I'll agree with you on the warnings. What happened was that after developing it under Windows, when I tried it the first time on Linux, I didn't actually see the warnings until long after I'd published it.

I apologize in advance, but I don't run any program without running perl -c against it first, even for trivial edits. Many programs spew data (or runtime warnings) causing compiler warnings to scroll off the buffer, never to be seen again.