Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.msdos.programmer > #980
| From | "Bill Buckels" <bbuckels@mts.net> |
|---|---|
| Newsgroups | comp.os.msdos.programmer |
| Subject | Re: Borlands Tasm5, procdesc using qword never works ? |
| Date | 2013-08-30 17:56 -0500 |
| Organization | Aioe.org NNTP Server |
| Message-ID | <kvr7va$d3k$1@speranza.aioe.org> (permalink) |
| References | <5220b3e9$0$15879$e4fe514c@news2.news.xs4all.nl> <kvqeb0$5de$1@speranza.aioe.org> <52211707$0$15872$e4fe514c@news2.news.xs4all.nl> |
"R.Wieser" <address@not.available> wrote: > You gave me something to look at and which *could* help me further. In > that regard you didn't do so bad. So thanks. :-) And I had some fun pulling your leg... your evidence indicates a problem parsing data types. In 1986 Aztec C65's native mode and cross-compiler for Apple II programs were released concurrently. Both Pseudo code compilers supported floats and doubles, and the MS-DOS cross-compiler supported floats and doubles, but the programmer had forgot to add the two enumerated data types to their Apple II ProDOS native mode compiler, and it has remained that way every since... Through that same period, Microsoft C released version 5.0 with a bugfix version 5.1 Summer of 87. MSC6 followed afew years later with several major bug fixes and was fully "Ansified". Sorta! Then Windows 3.1 came along and we slowly lost DOS. But many early undocumented features and typos in manuals make this an interesting exercise. I recall one manual of BIOS calls that inadvertently provided sample code to reformat a drive rather than read one. They had duplicated the same call twice, and went to print without catching the error. And it was never spotted in subsequent printing. Most guys never bothered much with Tasm. Most shops here used Masm. It was the hobby guys that bought Turbo C around here in those years, so perhaps the problem was never spotted until years later and fixed in later versions but not yours. I am certain that your tenacity will resolve this. Bill
Back to comp.os.msdos.programmer | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Borlands Tasm5, procdesc using qword never works ? "R.Wieser" <address@not.available> - 2013-08-30 17:02 +0200
Re: Borlands Tasm5, procdesc using qword never works ? "Bill Buckels" <bbuckels@mts.net> - 2013-08-30 10:39 -0500
Re: Borlands Tasm5, procdesc using qword never works ? "R.Wieser" <address@not.available> - 2013-08-31 00:05 +0200
Re: Borlands Tasm5, procdesc using qword never works ? "Bill Buckels" <bbuckels@mts.net> - 2013-08-30 17:56 -0500
Re: Borlands Tasm5, procdesc using qword never works ? "R.Wieser" <address@not.available> - 2013-08-31 10:43 +0200
Re: Borlands Tasm5, procdesc using qword never works ? JJ <duh@nah.meh> - 2013-08-31 18:34 +0700
Re: Borlands Tasm5, procdesc using qword never works ? "R.Wieser" <address@not.available> - 2013-08-31 15:21 +0200
Re: Borlands Tasm5, procdesc using qword never works ? JJ <duh@nah.meh> - 2013-08-31 22:13 +0700
Re: Borlands Tasm5, procdesc using qword never works ? "R.Wieser" <address@not.available> - 2013-08-31 18:21 +0200
Re: Borlands Tasm5, procdesc using qword never works ? "R.Wieser" <address@not.available> - 2013-09-01 10:38 +0200
Re: Borlands Tasm5, procdesc using qword never works ? "R.Wieser" <address@not.available> - 2013-09-03 12:37 +0200
csiph-web