<< Previous Message Main Index Next Message >>
<< Previous Message in Thread This Month Next Message in Thread >>
Date   : Thu, 04 Nov 2010 17:28:38 +0000
From   : groupsstuff@... (Farlie A)
Subject: Programming: Colour names in Sigsumeidsi

J.G.Harston wrote:
> Farlie A wrote:
>   
>> Sometimes a seeming math operation will be sued when defining a number,
>> hence
>> (&FF = is hexitiduna   = &100-1 )
>>     
>
> You've got the roman numbers problem. Is 9 represented as 5+4 or 10-1?
> You've shown that 255 is 256-1, but what's 254? 253? 252? At what point
> do you go from 128+64+32+16+something to 256-something?
>
> If you have no subtractions, it's easy, it's named bit positions:
> MID$("octit",(n%AND128)<>0)+MID$("teti",(n%AND64)<>0)+etc...
> just like converting an access byte to an access string.
>
> You haven't given enough examples to see the naming pattern, or
> enough rules to define it.
>
>   
OK, That's accepted, I need to think more on this it seems.

 For the moment, assume the bit position format (oct'et bi'd  style) as 
that's easier to code. (Treat the hexitiduna form as a shorthand... ;) )

&FF using bit position method would be "oct'etbi'dit oct'etbi'd " which 
whilst correct is longer than writing 'hexitiduna'

For reference here's some examples of the two formats side by side....

&FF hexitiduna  -       oct'etbi'ditoct'etbi'd
&FE hexitbiuna  -       oct'etbi'ditoct'etbi
&FD hexitbi'dduna -   oct'etbi'ditoct'etid
&FC  hexit'etuna    -   oct'etiditoct'et
&FB  hexit'etiduna -   oct'etbi'doctbi'd
...
&C0  hexit'etit una - oct'etit
&BF  oct'etitiduna  - oct'etitoct'etb'id
etc...

>> For example a simple dark green might be :
>>  ov   ga    bi rip (Overflow green accumlater 1/2  level.)
>>     
>     full green 2  divide
>
> Why not gaoctit ? green-8-times16
>
>   
value  -> register  convention in the language.   ga octit as a 
construct wouldn't make sense...
But that leads to a further question...  why not  ov bi rip ga ?

>> Whereas an obvious but not staurated green might be :
>>  ov   ga    tet rip    id bi mul (overflow green accumulator 3/4 level)
>>     
>     full green 4   divide 1  2  multiply
>
> Hmmm. I think I see where you're going here.
>
>   
>> For convenience , ovra is considered equivalent to
>> hex it      udna ra  nul ba     nul ga even though ovra is
>>     
>    16  times16  ??  red 0   blue   0   green
>
> I do vaguely remember a challenge to convert RGB values to
> colours names years'n'years ago. Pale yellow shading to green. ;)
>
>   
The curse of typo strikes again :
 hex it id una ra nul ba nul ga 
16 *16 1 - red 0 blue 0 green


>> PRINT FNTimeToText(4*60 + 30)
>>     
> Half past 4
>   
Don't get me started on how 'time' (or for that matter angular measure) 
is defined in Sigsumeidsi.  <crazy straight jacket face>
<< Previous Message Main Index Next Message >>
<< Previous Message in Thread This Month Next Message in Thread >>