Tirritate fans of OOP and BASIC by insisting that they be combined:10 LET #1 = "HELLO
-
Tirritate fans of OOP and BASIC by insisting that they be combined:
10 LET #1 = "HELLO.TXT".OPEN "O"
20 "Hello, world!".PRINT #1
30 #1.CLOSE
40 13.SCREEN
50 (100, 100).CIRCLE 80
60 LINE.INPUT: REM wait for enter key
70 0.SCREEN.CLS: REM Method chaining!
80 END -
Tirritate fans of OOP and BASIC by insisting that they be combined:
10 LET #1 = "HELLO.TXT".OPEN "O"
20 "Hello, world!".PRINT #1
30 #1.CLOSE
40 13.SCREEN
50 (100, 100).CIRCLE 80
60 LINE.INPUT: REM wait for enter key
70 0.SCREEN.CLS: REM Method chaining!
80 END@riley I'd like to replace line 80 with:
80 PROGRAM.END
-
@riley I'd like to replace line 80 with:
80 PROGRAM.END
@Uilebheist That would probably be among Microsoft's innovation for QOOP.BASIC, which introduces Structured Features(tm), and changes the syntax of
OPENtoLET #1 = "HELLO.TXT".OPEN(INPUT.FOR) -
@Uilebheist That would probably be among Microsoft's innovation for QOOP.BASIC, which introduces Structured Features(tm), and changes the syntax of
OPENtoLET #1 = "HELLO.TXT".OPEN(INPUT.FOR)@Uilebheist Speaking of method chaining, I kind of suspect there would be a real utility to inventing a notation that means "call this method, ignore what it returns, and let me attach another method call to the same object without explicitly stating its name". Perhaps
13->{Screen(); Cls();}? -
undefined oblomov@sociale.network shared this topic