- Als neu kennzeichnen
- Lesezeichen
- Abonnieren
- Stummschalten
- RSS-Feed abonnieren
- Kennzeichnen
- Anstößigen Inhalt melden
I have a graphics program that also generatesPRINT statements, and accepts input via READ statements.
I sometimes get this "severe error" in Unit 4. It doesn't like the input from the READ * statement. This is entirely RANDOM. Sometimes it accepts it, sometimes it doesn't. Even with the exact same input characters the error occurs randomly. I am not putting in any unusual characters, just numerical digits, periods, plus and minus signs.
READ and PRINT statements don't belong in the same window as graphics output anyway. Isn't there a way to ISOLATE those from the graphics? None of these problems occur in a console application.
An intelligent system programmer should provide for that.
Don't they TEST this stuff ????
Link kopiert
- Als neu kennzeichnen
- Lesezeichen
- Abonnieren
- Stummschalten
- RSS-Feed abonnieren
- Kennzeichnen
- Anstößigen Inhalt melden
- Als neu kennzeichnen
- Lesezeichen
- Abonnieren
- Stummschalten
- RSS-Feed abonnieren
- Kennzeichnen
- Anstößigen Inhalt melden
That's exactly what I need - a way to open a window so that CONIN$ comes from just that, and CONOUT$ goes to just that, so that READ and PRINT statements are isolated from the graphics I/O.
Is there an article I can read where this is discussed in more detail? I don't find that just the listings of the subroutine usages are that useful, it's so fragmented.
Thanks; Bill S.
- Als neu kennzeichnen
- Lesezeichen
- Abonnieren
- Stummschalten
- RSS-Feed abonnieren
- Kennzeichnen
- Anstößigen Inhalt melden
- RSS-Feed abonnieren
- Thema als neu kennzeichnen
- Thema als gelesen kennzeichnen
- Diesen Thema für aktuellen Benutzer floaten
- Lesezeichen
- Abonnieren
- Drucker-Anzeigeseite