a E i - Commodore Is Awesome
a E i - Commodore Is Awesome
a E i - Commodore Is Awesome
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
On The Blink<br />
C<br />
Drop a whatever you're doing and read<br />
on.<br />
i<br />
l How many times have you been<br />
developing i a large scale Basic program<br />
n<br />
and wished that there was an<br />
easier way? Now there is because<br />
g<br />
Blinker-64 from Information Develop-<br />
a<br />
ment Systems has come to your rescue.<br />
l Just what is Blinker-64? The<br />
answer l is quite simple: Bunker-64 is a<br />
linkage B editor for Basic programs. It<br />
enables a programs to be constructed<br />
from s a number of small modules<br />
stored i as files on one or more disks.<br />
c The main advantages to this<br />
approach p to programming are firstly<br />
that<br />
r<br />
small modules or subroutines are<br />
easier o to handle, edit arid debug.<br />
Secondly, g programming in Basic is<br />
made more productive and enjoyable.<br />
r<br />
Modules developed for one program<br />
a<br />
can be saved as part of a library of<br />
m<br />
modules and used as component parts<br />
of mothers<br />
as easily as standard Basic<br />
statements. e As your library grows, so<br />
your r ability to produce larger and<br />
more s complex programs increases.<br />
! Basically, Blinker-64 allows the<br />
programmer to make up a program of<br />
subroutines, then knit them togther to<br />
form a whole, The following example<br />
should show this clearly.<br />
Normal Basic Program<br />
10 P0KE53280. 0:P0KE53281,0:<br />
POKE646.2<br />
15 GOSUB500<br />
20 PRINT "NOW IS THE TIME ETC<br />
ETC"<br />
20 GOSUB600<br />
30 PRINT "PRESS ANY KEY TO<br />
CONTINUE"<br />
40 GOSUB 700<br />
50 END<br />
500 P0KE53265, PEEK (53265) AND<br />
239<br />
510 RETURN<br />
C64 REVIEW<br />
Basic programmers take heart. This new software from<br />
Information Development Systems should make life a lot<br />
easier.<br />
By Paul Eves<br />
500 P0KE53265.PEEK (53265) OR 16<br />
620 RETURN<br />
700 WA1T198.1:POKE198,0<br />
720 RETURN<br />
As you can see, this program is<br />
made up of a number of subroutines,<br />
some may be called repeatedly, others<br />
only once. Trying to keep track of all<br />
these subroutines in a large program<br />
can become tiresome. Moreover the<br />
next time you write something else you<br />
have to re-do all the subroutines again<br />
which can become very monotonous.<br />
With h Blinker-64 the above<br />
program would look like this:<br />
Blinker-64 Program<br />
10 P0KE53280,0: P0KE53281,0:<br />
PO K E646,2<br />
20 GOSUB"SCREEN OFF"<br />
30 PRINT "NOW IS THE TIME ETC<br />
ETC"<br />
40 GOSUB "SCREEN ON"<br />
50 PR1Nr'PRESS ANY KEY TO<br />
CONTINUE"<br />
60 GOSUB "GET KEY"<br />
70 END<br />
The subroutines 'screen off',<br />
'screen on' and 'get key' would be<br />
individual files saved on your library<br />
disk.<br />
When Blinker-64 is invoked with<br />
your blink command, it runs through<br />
your BASE program (i.e. the one in<br />
memory). Whenever it comes across a<br />
GOSUB 'xxx', it fetches that<br />
subroutine from your disk and<br />
appends it at the end of your base<br />
program. After all operations have<br />
been done it renumbers the entire<br />
program, substituting your named<br />
subroutines for numbered ones.<br />
The above fi les are known as<br />
CODE files. One other use of Blinker-<br />
64 is the handling of DATA files.<br />
The principle is the same, with a<br />
couple of exceptions. Data files can<br />
only contain REM and DATA token<br />
words. Any other token word would<br />
YOUR COMMODORE january 1987<br />
56<br />
result in a fatal error.<br />
There is a maximum of 255 distinct<br />
module references that can be<br />
appended in a single run_ Line number<br />
values, previously considered important<br />
when appending or merging Basic<br />
programs, are now of little consequence.<br />
Blinker-64 always produces a<br />
correctly numbered program,<br />
regardless of line numbers in any<br />
constituency source module,<br />
Whenever Blinker-64 finishes a<br />
run, a summary screen is displayed<br />
giving some simple statistics about the<br />
linked program. The summary looks<br />
like this:<br />
1. Start of BASIC — Lower limit of<br />
BASIC memory area<br />
2. Start of VARIABLES — End address<br />
of BASIC program<br />
3. Top of BASIC — Upper limit of<br />
BASIC memory area<br />
4. CODE modules named — Number of<br />
Code modules included, including<br />
base mod.<br />
5. CODE modules included — Number<br />
of modules in linked program<br />
6. DATA modules named — Number<br />
of DATA modules specified on<br />
command line<br />
7. DATA Modules included —Number<br />
of DATA modules included in linked<br />
program<br />
8, Bad Filenames — Number of illegal<br />
module references encountered<br />
9. Bad line numbers — Number of<br />
illegal line numbers encountered.<br />
There is so much more I could say<br />
about the program, unfortunately<br />
space is running out. All I need say is<br />
that after trying this program out. I felt<br />
that no Basic programmer should be<br />
without it.<br />
Touchline<br />
Company: Information Development<br />
Systems. Address: 24 Deerings Rd,<br />
Reigate, Surrey. Tel; 07372 22755<br />
Price: 129.90.