• ! The optimizer could hang under rare circumstances. Fixed.
  
• ! The csrlin() routine had a bug reporting sometimes the wrong position (this also affected Input() library which uses it). Fixed.
  
  
• + Every BEEP command always took 21 bytes. Now it only takes 11 bytes and it's faster (good for sound effects) if only constant numbers are used. So beep <num1>, <num2> is much optimized.
  
• DRAW routine has been improved for speed. Now it's 200% faster (aprox.) and takes only 150 bytes more.
  
• PLOT, DRAW & CIRCLE now uses SCREEN_ADD positioning => you can "DRAW" at part of the memory pointed by this internal variable.

• If several constant beeps (BEEP <num1>, <num2>) are specified one after another, they will be "compressed" and played with a beep sequencer. So every beep in the sequence takes only 4 bytes.
  
• A new library routine is in preparation: polyline, which draws a sequence of lines to coords Xn, Yn:
  
  Code:

  REM A list of coords (Unsigned Bytes)
DIM CoordList(10, 2) as UByte = { {1, 1}, {3, 100}, {20, 80}, ... _
                        ... ' More coord lists
                     {128, 189}}

REM Draws a polilyne of 10 coordinates, taking coord 0 as the 1st one
REM The 2nd 0 is mondatory, but useless here.
PolyLine(10, @CoordList(0, 0))
• UBound and LBound soon to come (for getting the Upper and Lower bound of arrays).
  
  Code:

  DIM a(2 To 5, 1 TO 8) as Byte

PRINT Ubound(a, 1) : REM prints 2
PRINT LBound(a, 2) : REM prints 8
• Variable parameters function calls, like in FreeBasic or C
  
  Code:

  Function Avg(n as uByte, ...)
    ...
End Function

PRINT Avg(3, 2.5, 3.6, 7.8)
PRINT Avg(5, 1, 4, 5, 7, 9)
  This way, function AVG can receive any numbers of parameters of any type.

LTee Wrote:Seems to be working fine, although I do get a "input.bas:38: warning: Empty loop" message every time I compile my code. Is that anything to worry about?

LCD Wrote:

LTee Wrote:Seems to be working fine, although I do get a "input.bas:38: warning: Empty loop" message every time I compile my code. Is that anything to worry about?

It is just a warning, not a error. Its just saying: Your code does not do anything.

LCD Wrote:If you make a procedure and do not use it, you will get warnings too, because procedures that are not used, are a waste of time and ressources. :mrgreen:

Quote:@Boriel: Any example how SCREEN_ADD can be used?