Amiga Knowledge Base

ID #1103

Anleitung Avanti

Avanti Anleitung/Handbuch in deutsch

mit freundlicher Genehmigung von AmigaHardwareWorld - Jörg Brenner

In der Anleitung wird erklärt:

Der Einbau in den Amiga 500

Der Einbau in den Amiga 2000

Installation einer FPU auf Avanti

Testen von Avanti

Testen der FPU

Die Software

Die FPU Software

Jumper und deren Funktion

Avanti läuft nicht

Die Auswahl der richtigen FPU

Tags: -

Verwandte Artikel:

Letzte Änderung des Artikels: 2008-05-17 02:49
Revision: 1.0

Digg it! Artikel ausdrucken Artikel weiterempfehlen Als PDF-Datei anzeigen
Übersetzungsvorschlag für Übersetzungsvorschlag für
Bewertung der Nützlichkeit dieses Artikels:

Durchschnittliche Bewertung: 0 von 5 (0 Bewertungen)

vollkommen überflüssig 1 2 3 4 5 sehr wertvoll

Es ist möglich, diesen Artikel zu kommentieren

Kommentar von Sejal:
Hi Cedric and all,I've still got letters from Tim Sweeney datnig back to the early days of Epic Megagames (when Jack Jazzrabbit was in development, way before the first line of code of the first Unreal had been written and even before everybody had Internet access). One of my all-time Tim favorites is a paper on how the game state replication was done in Unreal, written in 1999 by Tim Sweeney. It is still good today and was just plain visionary back in the days.You didn't emphasize on something very important he's saying now: we're moving to more complex systems and Type inference doesn't scale.Funny how everybody who responded so far talked about Nice, JML, Jetbrains's annotations.jar (@NotNull/@Nullable), etc. There are obviously people who want more control . And I'm one of these people (I do use IDEA 5.x/JDK 1.5 and @NotNull is a real time-saver): the stricter the limit you put on your abstract data types, the easier you make it for the compiler to proove that the various components will act as their contract say they will, the sooner you catch bugs, etc.You didn't mention it directly but he also talks about the benefits of referential transparency (one obvious advantage being to allow the use of memoization [yup, without an 'r'], one other advantage being to help the compiler proove the correctness of some part of the program).I side with everybody who recommends functional programming (and Joshua Bloch hints that it is possible to program in Java in a more functional way that what is usually seen, Effective Java item 13).And I side with everybody who's horrified by the horrible abuse of exceptions (the glorified goto's) in Java and C#.It is really good to see his hard data backing his statements on all the defects Java has and terminating the presentation with a full page devoted to one of Haskell's main flaw: type inference doesn't scale.I hope that the next mainstream programming language will ressemble the best of several worlds (I've got my idea as to how it should look like And I'm more than convinced it is *very* similar to Tim Sweeney's view).Really a good read, thanks for that nice blog entry,(I'll go check those Spec# slides now )
Added at: 2012-08-05 12:31

Kommentar von OzHpYPDV:
xretz7 cmcmzsoxubou
Added at: 2012-08-06 02:45

Kommentar von QPOGAevythFDuirUpiI:
iwB7oz iydagkzbgybx
Added at: 2012-08-07 08:40