Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.os.vms    |    DEC's VAX* line of computers & VMS.    |    264,096 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 264,027 of 264,096    |
|    Stephen Hoffman to gcalliet    |
|    Re: pictures in the old time    |
|    15 Jan 26 12:40:12    |
      From: seaohveh@hoffmanlabs.invalid              On 2026-01-13 15:35:23 +0000, gcalliet said:              > Hello,       >       > I begin the year - I hope successfull, happy, and with a good health       > for everyone with a somehow prehistoric question.       >       > Some applications, in general using x11, where linked with this sort of       > library:       > VAXCRTLG_D56_TV_AV.EXE;1       > VAXCRTLG_D56_V73_TV_AV.EXE;1       > VAXCRTL_D56_TV_AV.EXE;1       > VAXCRTL_D56_V73_TV_AV.EXE;1       >       > There are been vesting from VAX to alpha, and doing the same sort of       > operation to itanium.       >       > What has been done for x86? I know some applications using this sort of       > libraries, and without them it's impossible to go ahead.       >       > What has been done? What can be done?       >       > All information wellcomed.       >       > Gérard Calliet              I remember porting VAX C K&R-era code to DEC C back in the 1980s. More       than a little of that K&R C code my own. Fixing issues. It's       exceedingly rare to find VAX C code that isn't unstable at best, and       bggy, flaky, and crash-prone. Including my own.              The then-new DEC C / ANSI C diagnostics found all sorts of questionable       code and all too often found latent run-time errors. Which for some       developers and some projects meant workarounds were then used to avoid       fixing the informationals and the detected errors.              Here we are, some thirty years on, seemingly preserving that same       usually-buggy C code, whether because of budgets or regulations or       whatever, or maybe because the source code was lost.              I'd be surprised "if rendering picture by Motif+x11" was still the case       for DECwindows and its apps on Alpha and later, but can fully believe       some unidentified Motif tools somewhere were translated and never       remediated.              If some VAX C code is linked against VAXCRTLG or its derivatives, run.       Run far away. That's G_Float code, and quite possibly VAX C code       written for MicroVAX I or VAXstation.              If y'all want to discuss which (or whose) DECwindows Motif apps are       involved, and whether the source code is available, have at...                            --       Pure Personal Opinion | HoffmanLabs LLC              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca