Re: [cc65] range error

On Monday 16 January 2012, you wrote:
> >> if
> >> .byte 3,2,1,0,-1,-2,-3
> >> is not compiling I find this annoying
> > 
> > Ok. Which values would you then consider legal? Do you want anything
> > truncated to 8 bits? Or just -128..255? How about
> > 
> >         .byte   $FFFFFF80
> > 
> > where the argument has the same internal representation as -128, should
> > that trigger an error?
> 
> If the size is clear, just silently truncate it to 8bit, if the size is
> not clear throw an error.
> If you truncate silently, give a warning (optional).
> I mean this is as far as I see only an issue for constants.
> 
> Maybe I do not oversee all the consequences, but I consider this a coder
> friendly solution.

thats what i would expect too. ie .word  $FFFFFF80 should truncate to 16. etc 
pp

-- 

http://www.hitmen-console.org    http://magicdisk.untergrund.net
http://www.pokefinder.org        http://ftp.pokefinder.org

Very few people do anything creative after the age of thirty-five. The reason 
is that very few people do anything creative before the age of thirty-five 
<Joel Hildebrand>

----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo@musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.