| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | `Which C++ Compiler?` -- |
JdBP> problems in other vendors' debuggers as well, and apart from the SVGA
JdBP> display problems (which are listed as CONS) and the occasional lockup
Well, with such a serious problem (do you know any developer who willingly
runs at 640x480x16?) I just thought it odd that it is introduced as
"good" when other's are not.
> JdeBP> Supports
> JdeBP> customisable function calling conventions.
>
> Watcom supports this as well.
PF>
JdBP> Fine. Out of interest ... how ? All that I have
It's kinda knarly, but works well -- and even the optimizer takes
advantage of it. Here's an example; in this case, I am redefining one of
the built in types:
#pragma aux fortran "^" \
loadds \
parm reverse routine [] \
value struct float struct caller[] \
modify [ax bx cx dx es];
JdBP> provides. Does Watcom support (for example) controlling whether
JdBP> floating point return values are returned on the x87 stack or in
JdBP> registers on a function by function basis ?
Yes.
--- Maximus/2 2.02p1
* Origin: Sol 3/Toronto (905)858-8488 (1:259/414)SEEN-BY: 105/42 620/243 711/401 409 410 413 430 807 808 809 934 955 712/407 SEEN-BY: 712/515 628 704 713/888 800/1 7877/2809 @PATH: 259/414 400 99 250/702 3615/50 396/1 270/101 105/103 42 712/515 @PATH: 711/808 809 934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.