Mail Archives: djgpp/2000/07/19/11:10:05
Radical NetSurfer <radsmail AT juno DOT com> wrote:
> |> First of all, (trust me here):
> |> cprintf CAN BE re-directed; _IF_ properly implemented!
> | Says who? Who defines 'proper' implementation of cprintf()?
> As one small example, VBDOS 1.0 allows cprintf to be redirected:
> colored text if no re-dir; normal ASCII chars to wherever re-dired.
What's VBDOS? A compiler for C programs? Another programming language?
An application? How does it document its implementation of 'cprintf'?
Sorry if all this sounds a bit overly picky, but to me, it seems like
you're jumping to conclusions. From applications' apparent behaviour
directly to how library function calls should (or do) behave.
> If anyone should happen to know how to write a little MS-Windows 3.1
> 'C' style Code... you're help is also needed.
You won't find many people with such knowledge in *this* newsgroup, I
think. Even with the help of Win32s and RSXNTDJ or MinGW, gcc cannot
make programs on Windows 3.1 platforms. You can compile programs
that'll work there, but the compiler itself doesn't work on 3.1
If you really want to code for Windows 3.1, try to get your hand on an
old copy of Charles Petzold's "Programming Windows", the version
dealing with 16bit Windows. That's _the_ one book any Windows
programmer using the raw C API instead of C++ class libraries
absolutely has to have. You won't get almost anywhere without it.
--
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.
- Raw text -