I second that idea to use streams instead of old C formating.
We can use ostrstream, or better, ostringstream classes
-Fred
- Original Message -
From: Jon Berndt [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, May 01, 2002 5:15 AM
Subject: RE: [Flightgear-devel] JSBSim Build
Here is one you will all like. It appears as if MSVC does not define
snprintf() in any of its headers, but it does have _snprintf() with the
same parameter list. RG!
In JSBSim/FGFCS.cpp, I had to add a #define to map _snprintf() to snprintf(
) in order to get the latest CVS updates
On Tue, 2002-04-30 at 17:24, Jonathan Polley wrote:
Here is one you will all like. It appears as if MSVC does not define
snprintf() in any of its headers, but it does have _snprintf() with the
same parameter list. RG!
In JSBSim/FGFCS.cpp, I had to add a #define to map
On Tuesday, April 30, 2002, at 08:57 PM, Tony Peden wrote:
On Tue, 2002-04-30 at 17:24, Jonathan Polley wrote:
In JSBSim/FGFCS.cpp, I had to add a #define to map _snprintf() to
snprintf(
)
Sorry about that.
Does it make sense to have _snprintf() instead of snprintf()? I tried
defining
I'd prefer to get away from using _snprintf, snprintf, or whatever. The
only reason we use them (IIRC) is to limit the length of an output string.
This can be done in other ways, such as using the string class. Since they
would not be used in performance critical areas, maybe that's an option?
