#turboc — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #turboc, aggregated by home.social.
-
TIL there's a dosbox fork (dosbox-x) with a bunch of fancy features, including more realistic emulation of hercules monographics displays, which lets me more accurately re-experience my middle school XT clone computing experience.
-
TIL there's a dosbox fork (dosbox-x) with a bunch of fancy features, including more realistic emulation of hercules monographics displays, which lets me more accurately re-experience my middle school XT clone computing experience.
-
TIL there's a dosbox fork (dosbox-x) with a bunch of fancy features, including more realistic emulation of hercules monographics displays, which lets me more accurately re-experience my middle school XT clone computing experience.
-
TIL there's a dosbox fork (dosbox-x) with a bunch of fancy features, including more realistic emulation of hercules monographics displays, which lets me more accurately re-experience my middle school XT clone computing experience.
-
TIL there's a dosbox fork (dosbox-x) with a bunch of fancy features, including more realistic emulation of hercules monographics displays, which lets me more accurately re-experience my middle school XT clone computing experience.
-
I should have looked at the linker options more closely and turned on "Warn duplicate symbols" from the start...
-
I should have looked at the linker options more closely and turned on "Warn duplicate symbols" from the start...
-
I should have looked at the linker options more closely and turned on "Warn duplicate symbols" from the start...
-
I should have looked at the linker options more closely and turned on "Warn duplicate symbols" from the start...
-
I should have looked at the linker options more closely and turned on "Warn duplicate symbols" from the start...
-
Huh. For some reason Turbo C's time() is getting stuck in an infinite loop. Don't call it to seed the random number generator or determine the phase of moon and off we go...
Hmm. Can't get the time() hang to repro in a trivial test program. I wonder what's going on here.
Aha. time() called getdate() which conflicted with a function in Hack (that called getlt() that called time()). Not sure why that resulted in a hang instead of a crash due to stack overflow...
-
Huh. For some reason Turbo C's time() is getting stuck in an infinite loop. Don't call it to seed the random number generator or determine the phase of moon and off we go...
Hmm. Can't get the time() hang to repro in a trivial test program. I wonder what's going on here.
Aha. time() called getdate() which conflicted with a function in Hack (that called getlt() that called time()). Not sure why that resulted in a hang instead of a crash due to stack overflow...
-
Huh. For some reason Turbo C's time() is getting stuck in an infinite loop. Don't call it to seed the random number generator or determine the phase of moon and off we go...
Hmm. Can't get the time() hang to repro in a trivial test program. I wonder what's going on here.
Aha. time() called getdate() which conflicted with a function in Hack (that called getlt() that called time()). Not sure why that resulted in a hang instead of a crash due to stack overflow...
-
Huh. For some reason Turbo C's time() is getting stuck in an infinite loop. Don't call it to seed the random number generator or determine the phase of moon and off we go...
Hmm. Can't get the time() hang to repro in a trivial test program. I wonder what's going on here.
Aha. time() called getdate() which conflicted with a function in Hack (that called getlt() that called time()). Not sure why that resulted in a hang instead of a crash due to stack overflow...
-
Huh. For some reason Turbo C's time() is getting stuck in an infinite loop. Don't call it to seed the random number generator or determine the phase of moon and off we go...
Hmm. Can't get the time() hang to repro in a trivial test program. I wonder what's going on here.
Aha. time() called getdate() which conflicted with a function in Hack (that called getlt() that called time()). Not sure why that resulted in a hang instead of a crash due to stack overflow...
-
Well this sure brings back memories.
It runs a lot faster in DOSBOX than on the 10MHz 512KB Dual-360K-Floppy XT clone I originally ran it on when I was a kid.
Disk Images
https://archive.org/details/borland-turbo-c-v2.0User and Reference Manual:
https://archive.org/details/bitsavers_borlandturer2.01988_23162264
https://archive.org/details/bitsavers_borlandturuideVer2.01988_19310204If you copy all 6 disks into a single INSTALL directory, you can run INSTALL.EXE from there and it'll do its thing.
-
Well this sure brings back memories.
It runs a lot faster in DOSBOX than on the 10MHz 512KB Dual-360K-Floppy XT clone I originally ran it on when I was a kid.
Disk Images
https://archive.org/details/borland-turbo-c-v2.0User and Reference Manual:
https://archive.org/details/bitsavers_borlandturer2.01988_23162264
https://archive.org/details/bitsavers_borlandturuideVer2.01988_19310204If you copy all 6 disks into a single INSTALL directory, you can run INSTALL.EXE from there and it'll do its thing.
-
Well this sure brings back memories.
It runs a lot faster in DOSBOX than on the 10MHz 512KB Dual-360K-Floppy XT clone I originally ran it on when I was a kid.
Disk Images
https://archive.org/details/borland-turbo-c-v2.0User and Reference Manual:
https://archive.org/details/bitsavers_borlandturer2.01988_23162264
https://archive.org/details/bitsavers_borlandturuideVer2.01988_19310204If you copy all 6 disks into a single INSTALL directory, you can run INSTALL.EXE from there and it'll do its thing.
-
Well this sure brings back memories.
It runs a lot faster in DOSBOX than on the 10MHz 512KB Dual-360K-Floppy XT clone I originally ran it on when I was a kid.
Disk Images
https://archive.org/details/borland-turbo-c-v2.0User and Reference Manual:
https://archive.org/details/bitsavers_borlandturer2.01988_23162264
https://archive.org/details/bitsavers_borlandturuideVer2.01988_19310204If you copy all 6 disks into a single INSTALL directory, you can run INSTALL.EXE from there and it'll do its thing.
-
Well this sure brings back memories.
It runs a lot faster in DOSBOX than on the 10MHz 512KB Dual-360K-Floppy XT clone I originally ran it on when I was a kid.
Disk Images
https://archive.org/details/borland-turbo-c-v2.0User and Reference Manual:
https://archive.org/details/bitsavers_borlandturer2.01988_23162264
https://archive.org/details/bitsavers_borlandturuideVer2.01988_19310204If you copy all 6 disks into a single INSTALL directory, you can run INSTALL.EXE from there and it'll do its thing.
-
New video for Patrons:
Let's Code MS DOS 0x31: ANSI C Data Types
The C programming language has only few builtin data types. But for a beginner those can be a bit confusing. So we will have a look at what data types are offered, and what kind of new datatypes you can build with C.
-
New video for Patrons:
Let's Code MS DOS 0x31: ANSI C Data Types
The C programming language has only few builtin data types. But for a beginner those can be a bit confusing. So we will have a look at what data types are offered, and what kind of new datatypes you can build with C.
-
New video for Patrons:
Let's Code MS DOS 0x31: ANSI C Data Types
The C programming language has only few builtin data types. But for a beginner those can be a bit confusing. So we will have a look at what data types are offered, and what kind of new datatypes you can build with C.
-
New video for Patrons:
Let's Code MS DOS 0x31: ANSI C Data Types
The C programming language has only few builtin data types. But for a beginner those can be a bit confusing. So we will have a look at what data types are offered, and what kind of new datatypes you can build with C.
-
New video for Patrons:
Let's Code MS DOS 0x31: ANSI C Data Types
The C programming language has only few builtin data types. But for a beginner those can be a bit confusing. So we will have a look at what data types are offered, and what kind of new datatypes you can build with C.
-
Retro geek t-shirt 🤓 unfortunately it's an M and does not fit me, especially with these #poledance shoulders. 💪
#borland #TurboC #retrocomputing -
Retro geek t-shirt 🤓 unfortunately it's an M and does not fit me, especially with these #poledance shoulders. 💪
#borland #TurboC #retrocomputing -
Retro geek t-shirt 🤓 unfortunately it's an M and does not fit me, especially with these #poledance shoulders. 💪
#borland #TurboC #retrocomputing -
Retro geek t-shirt 🤓 unfortunately it's an M and does not fit me, especially with these #poledance shoulders. 💪
#borland #TurboC #retrocomputing -
Retro geek t-shirt 🤓 unfortunately it's an M and does not fit me, especially with these #poledance shoulders. 💪
#borland #TurboC #retrocomputing -
🚀 NEW on We ❤️ Open Source 🚀
Jim Hall takes us on a journey through C compilers! Explore the unique quirks of TurboC and Open Watcom, and see why “not everything is GNU C.”
Read now:
https://buff.ly/3E4vhib -
🚀 NEW on We ❤️ Open Source 🚀
Jim Hall takes us on a journey through C compilers! Explore the unique quirks of TurboC and Open Watcom, and see why “not everything is GNU C.”
Read now:
https://buff.ly/3E4vhib -
🚀 NEW on We ❤️ Open Source 🚀
Jim Hall takes us on a journey through C compilers! Explore the unique quirks of TurboC and Open Watcom, and see why “not everything is GNU C.”
Read now:
https://buff.ly/3E4vhib -
🚀 NEW on We ❤️ Open Source 🚀
Jim Hall takes us on a journey through C compilers! Explore the unique quirks of TurboC and Open Watcom, and see why “not everything is GNU C.”
Read now:
https://buff.ly/3E4vhib -
🚀 NEW on We ❤️ Open Source 🚀
Jim Hall takes us on a journey through C compilers! Explore the unique quirks of TurboC and Open Watcom, and see why “not everything is GNU C.”
Read now:
https://buff.ly/3E4vhib -
@jamesog i cut my language teeth on #BASIC and #Pascal on my #Apple2e (and a bunch of #PET and #TRS80) back in the day. By college (1988) I was using #C, #LISP, et al on a variety of systems. I used #TurboPascal and #TurboC on a few college projects. Oh and #shell scripting. Lots of shell scripting. Ironically, I never touched #COBOL until I began work after college. Hehe #RetroComputing
-
@jamesog i cut my language teeth on #BASIC and #Pascal on my #Apple2e (and a bunch of #PET and #TRS80) back in the day. By college (1988) I was using #C, #LISP, et al on a variety of systems. I used #TurboPascal and #TurboC on a few college projects. Oh and #shell scripting. Lots of shell scripting. Ironically, I never touched #COBOL until I began work after college. Hehe #RetroComputing
-
@jamesog i cut my language teeth on #BASIC and #Pascal on my #Apple2e (and a bunch of #PET and #TRS80) back in the day. By college (1988) I was using #C, #LISP, et al on a variety of systems. I used #TurboPascal and #TurboC on a few college projects. Oh and #shell scripting. Lots of shell scripting. Ironically, I never touched #COBOL until I began work after college. Hehe #RetroComputing
-
@jamesog i cut my language teeth on #BASIC and #Pascal on my #Apple2e (and a bunch of #PET and #TRS80) back in the day. By college (1988) I was using #C, #LISP, et al on a variety of systems. I used #TurboPascal and #TurboC on a few college projects. Oh and #shell scripting. Lots of shell scripting. Ironically, I never touched #COBOL until I began work after college. Hehe #RetroComputing
-
@jamesog i cut my language teeth on #BASIC and #Pascal on my #Apple2e (and a bunch of #PET and #TRS80) back in the day. By college (1988) I was using #C, #LISP, et al on a variety of systems. I used #TurboPascal and #TurboC on a few college projects. Oh and #shell scripting. Lots of shell scripting. Ironically, I never touched #COBOL until I began work after college. Hehe #RetroComputing
-
Hm, I think Turbo C 2.01 has a very tricky, and VERY ancient bug. The intr() function from <dos.h> header SHOULD be able to pass ES:BP pointers to interrupts. However I think it doesn't. Using this gives garbage (or probably: the stack pointer) to the interrupt vector instead. I wonder if this could be patched...? How hard can it be to disassemble the .lib files?
#retrocomputing #turboc #letscode -
Hm, I think Turbo C 2.01 has a very tricky, and VERY ancient bug. The intr() function from <dos.h> header SHOULD be able to pass ES:BP pointers to interrupts. However I think it doesn't. Using this gives garbage (or probably: the stack pointer) to the interrupt vector instead. I wonder if this could be patched...? How hard can it be to disassemble the .lib files?
#retrocomputing #turboc #letscode -
Hm, I think Turbo C 2.01 has a very tricky, and VERY ancient bug. The intr() function from <dos.h> header SHOULD be able to pass ES:BP pointers to interrupts. However I think it doesn't. Using this gives garbage (or probably: the stack pointer) to the interrupt vector instead. I wonder if this could be patched...? How hard can it be to disassemble the .lib files?
#retrocomputing #turboc #letscode -
Hm, I think Turbo C 2.01 has a very tricky, and VERY ancient bug. The intr() function from <dos.h> header SHOULD be able to pass ES:BP pointers to interrupts. However I think it doesn't. Using this gives garbage (or probably: the stack pointer) to the interrupt vector instead. I wonder if this could be patched...? How hard can it be to disassemble the .lib files?
#retrocomputing #turboc #letscode -
Hm, I think Turbo C 2.01 has a very tricky, and VERY ancient bug. The intr() function from <dos.h> header SHOULD be able to pass ES:BP pointers to interrupts. However I think it doesn't. Using this gives garbage (or probably: the stack pointer) to the interrupt vector instead. I wonder if this could be patched...? How hard can it be to disassemble the .lib files?
#retrocomputing #turboc #letscode