| Posted By
SVS
on 2012-01-01
06:59:26
 |  Austrospeed translation
Hello and happy new year to you.
I would ask German plussiers for translate the review of AustroSpeed +4 appeared on Compute Mit SA 4/87. http://plus4world.powweb.com/publications/Compute_Mit_SA_4_87
It should be an interested completion of the recent developments on this great piece of software.
Thank you.
|
|
Posted By
rudis
on 2012-01-01
09:27:32
 | Re: Austrospeed translation
don't have these.
is a pdf or other source available?
|
|
Posted By
Rüdiger
on 2012-01-01
10:43:11
| Re: Austrospeed translation
In the 64er Sonderheft 14/87 is another big report about Austrospeed +4. Interested?
|
|
Posted By
rudis
on 2012-01-01
10:59:40
| Re: Austrospeed translation
wenn die digital vorliegt, könnte man die doch schnell durch google jagen..
|
|
Posted By
MMS
on 2012-01-01
11:16:20
 | Re: Austrospeed translation
ja, ja, und übersetzen  with Google, but will be funny, I think.
|
|
Posted By
rudis
on 2012-01-01
11:28:09
| Re: Austrospeed translation
yes
http://translate.google.de/
|
|
Posted By
Chicken
on 2012-01-01
11:54:47
 | Re: Austrospeed translation
SVS,
everything interesting in there I did translate a long time ago  That's the part about the "RESUME" (which they might got wrong). Everything else wouldn't add anything to the things we already now. Check out the old thread on Austrospeed, it's in there.
I don't know the article Rudiger mentioned but that one could be more interesting.
Unfortunately, "Google translate" from German to English is lousy at best (Though, it's definitely better than nothing ). The other way around it's usable. Anyway... I wouldn't mind translating - whenever I have the article and enough time - but I think a brief summary would be enough to cover the interesting points.
|
|
Posted By
C16 Chris
on 2012-01-01
16:05:20
 | Re: Austrospeed translation
Programm: AUSTRO-SPEED- PLUS
System: Plus 4 Preis: ca.149 DM Bezugsquelle: R. Lindensch- midt, Schulstraße 14, 4972 Löhne 2, Tel. 05732/72849
AUSTRO-SPEED ist kein neuer Compiler, denn die erste G64 Version dieses Compilerers exe- stierte schon kurz nachdem dieser auf den Markt kam. Obwohl der C64 Compiler bis heute kaum verändert wurde, gilt er nach wie vor als einer der leistungsfähigsten Basic-Compiler. Nicht zuletzt aus diesem Grund war ich deshalb gespannt wie gut die Adaption auf dem PLUS 4 gelungen ist.
Geliefert wird der Compiler zusammen mit einem HardwareSteckmodul. Dieses Steckmodul, welches in den User-Port eingesteckt wird, soll verhindern das Raubkopierer dem Programm zu nahe rücken. Das eigentliche Programm befindet sich auf einer Diskette und belegt 116 Blocks (29580 Bytes). Nachdem man das Steckmodul eingesteckt und den Compiler geladen hat, meldet sich dieser mit folgendem Haupt-
1. Single Floppy (Resume nur mit Zeilennummer)
2. Dual Drive Floppy (Resume nur mit Zeilennummer)
3. 2 Diskettenstationen (Resume nur mit Zeilennummer)
4. Single Floppy (Resume komplett)
5. Dual Drive Floppy (Resume komplett)
6. 2 Diskettenstationen (Resume komplett)
Bei den ersten drei Menüpunkten darf nach dem Basic RESUME- Befehl nur eine Zeilennummer (keine Variable) folgen. Bei einem Fehler werden alle Rücksprung- adressen (GOSUB) gelöscht und alle FOR..NEXT Schleifen abgeschlossen. Die Menüpunkte 4, 5 und 6 erlauben auch RESUME (Befehl wiederholen) und RESUME NEXT (nächsten Befehl ausführen). Nachteil bei den letzten drei Menüpunkten ist allerdings, daß das erzeugte Programm etwa 5 bis 10% langsamer und der P- Code circa 20 % länger als bei den Punkten 1,2 und 3 ist. Bei den Punkten 4,5 und 6 wird also der Stackpointer nicht verändert.
Hat man sich für einen Menüpunkt entschieden so fragt der Compiler nach dem zu compilie- renden Basic-Filenamen. Ab hier arbeitet der Compiler identisch mit. der C64 Version. Aus diesem Grund liegt dem Compiler auch eine C64 Anleitung bei, wobei ein Merkblatt die Unterschiede der PLUS4 Version darlegt.
Die Unterschiede bestehen vor allem darin, das die STOP-Taste nicht mehr abgefragt wird. Bei den Befehlen GRAPHIC und CLR wird nur die GRAPHIC 0
ausgeführt. Die 10 kByte für HI- RES Bildschirm werden nicht freigegeben. Wenn während des Compilervorganges ein GRA- PHIC-Befehl vorkommt, wird automatisch der Programmbe- . ginn auf FiEX 4000 festgelegt.
Neben diesen Unterschieden, sowie kleinen Einschränkungen bei den Befehlen TRAP und RESUME wird neben dem Standard- Basic 2.0 auch der komplette Befehlssatz des PLUS 4 compiliert.
AUSTRO-SPEED erzeugt keinen echten Maschinencode, sondern einen sogenannten P-Code. Mit einem schnellen Maschinenprogramm (RUN-TIME Routinen), das ca. 4 kByte belegt, wird der P-Code zusammen als ein ablauffähiges Objektfile abgelegt. Dieses File kann später einfach mit LOAD geladen und mit einem RUN gestartet werden.
Der eigentliche Compiliervor- gang geht in zwei Durchläufen (2 Pass-Compiler) vor sich, wobei sich die Compilerdauer je nach
Programmlänge bis zu einige Minuten dauern kann. Im Test wurde beispielsweise ein 31 Block langes Basic Programm in 4 Minuten compiliert. Das erzeugte Objekt-
file besaß nach dem Compilervorgang eine Länge von 56 Blocks.
Neben dem ablauffähigen Programm erzeugt der Compiler auch ein sogenanntes Zeilennum- mer-Fiie. Diese Datei erlaubt nachträglich festzustellen, ab welcher Speicherstelle eine bestimmte Zeile abgelegt ist. Das eigentliche Programmfile ist zwar fast immer länger als das compilierte Basic- Programm, besitzt jed.oeh eine durchschnittlich eine 2 bis 10 Fach schnellere Ausführungszeit. Gerade bei Spielprogrammen aber auch bei komplexen Anwendungen (z.B. Sortieralgorithmus) dürfte sich ein solcher Geschwindigkeitsvorteil sehr angenehm auswirken.
Etwas nachteilig zeigte sich der Compiler bei eingebauten Maschinenprogrammen, welche in Form von DATA-Zeilen abgelegt sind und in den Basic Speicherbereich gepokt werden. Bei solchen Programmen, die leider heute nur zu häufig sind, stürzte der Compiler regelmäßig ab.
Es liegt also an dem Programmierer wie effizient er mit dem wirklich hervorragenden Compiler AUSTRO-SPEED umgeht. Die Grundvorraussetzung für proffe- sionelles arbeiten, soweit in BASIC überhaupt möglich* werden jedoch durch den Compiler erheblich verbessert.
Google-translation (http://translate.google.de/) English:
Program: AUSTRO-SPEED PLUS
System Plus 4 Price: ca.149 DM Source: R. Lindensch - midt, Schulstraße 14, 4972 2 wages, Phone 05732/72849
AUSTRO-SPEED is not a new compiler, because the first version of this G64 Compilerers exe stared shortly after it came onto the market. Although the C64 compiler has changed very little, he is still regarded as one of the most powerful Basic compiler. This is a major reason why I was curious how good the adaptation is successful on the Plus 4.
The compiler is supplied together with a hardware plug-in module. This plug-in module that plugs into the user port to prevent the pirates to move the program to close. The actual program is located on a floppy disk and occupies 116 blocks (29 580 bytes). Once you have inserted the cartridge and loaded the compiler to report this with the following main
First Single floppy (resume only with line number)
Second Dual Floppy Drive (resume only with line number)
Third 2 floppy stations (resume only with line number)
4th Single floppy (resume complete)
5th Dual Floppy Drive (resume complete)
6th 2 floppy stations (resume complete)
The first three menu items must for the Basic RESUME command only a line number followed by (a variable). On error, return addresses be-all (GOSUB) and deleted all the FOR .. NEXT loops completed. The menu items 4, 5 and 6 allow (repeat command) and RESUME and RESUME NEXT (next run command). Disadvantage in the last three menu items, however, is that the generated program is slow about 5 to 10% and the P-code about 20% longer than the points 1,2 and 3. At the points 4,5 and 6 so the stack pointer is not changed.
If you have decided on a menu item then the compiler asks for the leaders to be compiled Basic file name. From here, the compiler works with the same. the C64 version. For this reason, the compiler is also a guide at C64, with a leaflet outlining the differences between the PLUS4 version.
The differences lie in the fact that the STOP button is not checked. The commands GRAPHIC and GRAPHIC CLR is only 0
carried out. The 10 Kbytes are for HI-RES screen is not released. If one occurs during the compiler process GRA-phic command will automatically program areas. set at the beginning FiEX 4000th
Besides these differences, as well as a few limitations in the TRAP and RESUME commands in addition to the standard Basic 2.0 and the complete instruction set of the 4 PLUS is compiled.
AUSTRO-SPEED produces no real machine code, but a so-called P-code. With a fast machine program (RUN-TIME routines), which occupies about 4 Kbytes, the P-code together as an executable object file is stored. This file can later be easily loaded with LOAD and started with a RUN.
The actual Compiliervor transition proceeds in two passes (two-pass compiler) before him, with the duration depending on the compiler
Program length may take up to several minutes. In the test, for example, a 31-block-long Basic program was compiled in 4 minutes. The created object-
file after the compiler process had a length of 56 blocks.
Besides the executable program, the compiler generates a so-called line number-Fiie. This file subsequently allows to determine which location is stored from a given row. The actual program file is almost always longer than the compiled Basic program that has an average jed.oeh a 2 to 10 specialist faster execution time. Especially in game programs but also for complex applications (eg sorting algorithm) is likely to affect such a speed advantage very pleasant.
Something detrimental to the compiler was built in machine programs, which are stored in the form of DATA lines and in the basic memory area gepokt. Such programs, which are unfortunately all too often today, fell regularly from the compiler.
It's up to the programmer as he efficiently deal with the really excellent compiler AUSTRO-SPEED. The basic prerequisite for Proff-sional work, as far as possible in BASIC at all * but considerably improved by the compiler.
Promt-translation (http://www.online-translator.com) English:
Programme: AUSTRO speed PLUS
System: Plus 4 prices: approx. 149 DM of source of supply: R. Lindensch-midt, Schulstrasse 14, 4972 wages 2, Tel. 05732/72849
AUSTRO speed is no new compiler, because the first G64 version this Compilerers exe-this stared quite briefly after came on the market. Although the C64 compiler was hardly changed till this day, he is still valid as one of the most efficient BASIC compilers. Therefore, not least that's why I was curious as well the adaptation on the PLUS 4 has succeeded.
The compiler is delivered together with a HardwareSteckmodul. This Steckmodul which is pocketed in the user's port should prevent move the bootlegger to the programme too near. The real programme is on a disk and books 116 blocks (29,580 bytes). After one has pocketed the Steckmodul and has loaded the compiler, this contacts with the following head
1. Single Floppy (Resume only with line number)
2. Dual drive Floppy (Resume only with line number)
3. 2 disk stations (Resume only with line number)
4. Single Floppy (Resume completely)
5. Dual drive Floppy (Resume completely)
6. 2 disk stations (Resume completely)
With the first three menu points only one line number (no variable) may follow after the BASIC RESUME-order. With a mistake addresses (GOSUB) are extinguished all back jump and all FOR. Loops NEXT concluded. The menu points 4, 5 and 6 also permit RESUME (order repeat) and RESUME NEXT (the next order explain). However, disadvantage with the last three menu points is that the generated programme is from about 5 to 10% more slowly and the P-code approximately 20% longer than with the points 1,2 and 3. With the points 4,5 and 6 the stack pointer is not changed.
If one has decided on a menu point so the compiler asks after to compilie-renden BASIC-file names. From the compiler co-operates here identically. the C64 version. That's why a C64 instructions is also enclosed to the compiler and a leaflet demonstrates the differences of the version PLUS4.
The differences consist in it above all which is not questioned the break switch any more. With the orders GRAPHIC and CLR becomes only the GRAPHIC 0
explained. 10 Kbyte for HI screen RES are not released. If during the compiler process a GRA-PHIC order seems, it is automatically fixed Programmbe-. ginn to FiEX 4000.
Beside these differences, as well as small restrictions with the orders TRAP and RESUME BASIC 2.0 becomes beside the standard also the complete instruction set of the PLUS 4 compiliert.
AUSTRO speed generates no real machine code, but a so-called P code. With a quick machine programme (RUN TIME routines) which books approx. 4 Kbyte the P code is filed together as an object file capable of expiry. This file can be loaded later simply with LOAD and be started with a RUN.
Real Compiliervor-way goes in two flows (2 passport compilers) vo
|
|
Posted By
Patrick
on 2012-01-01
16:50:53
| Re: Austrospeed translation
wow, c16 chris is back!!!
|
|
Posted By
SVS
on 2012-01-02
04:40:16
| Re: Austrospeed translation
Good! It is even spoken of limitations on TRAP and RESUME commands, that are where me and MikeZ met great problems.
Anyone has this info? Or the original leaflet?
|
|
Posted By
MMS
on 2012-01-02
06:52:33
| Re: Austrospeed translation
Well, reading the draft translation by Google I already found a VERY important note for me: most of integrated machine codes (DATA+SYS) will not work. (hm, maybe only in the low memory area, that should not be touched by Austrospeed)
It means that I should not choose such kind of sprite simulation, if I want to speed up the PRG with Autrospeed. On the other hand, GSHAPE and SSHAPE will have no benefits from Autrospeed at all, and loading pictures are easier with kernal routines (possible with normal LOAD too in BASIC, but then I should forget the idea of structured programe code, starting the BASIC program with a lot of load routines).
I would be great if those slow BASIC HIRES/MULTI routines (PAINT, DRAW, ) could be changed by the extended (fast) code, as I learned in this forum, these are slow mainly due to bank switching, and in the Hacking magasines I saw some 10-20x faster routines.
Final words: so it seems I cannot use Austrospeed for my project, but it is better to not plan it, and have the right approach from the very beginning and develop some small machine code routines to help on bottleneck speed issues.
|
|
Posted By
rudis
on 2012-01-02
11:38:51
| Re: Austrospeed translation
p-code was very hip at that time.
|
|
|
|
| |
Copyright © Plus/4 World Team, 2001-2024 |
