stdio.h ?

[\(ProteanThread\)]

can "stdio.h" be OS specific at the kernal level or ? i know what I'm
trying to ask here but not sure how to word it :-)
--
Woodzy
http://www.rtdos.com/forum

[Maxim S. Shatskih]

> Prior to Visual C++ 7.0

Is it Visual Studio 2003?

Sorry, I only use the Windows DDK to build and eVC++ 4.0 as pure text editor
(similar to VC++ 6 aka VS98 but newer a bit). So, I don't know much about newer
Visual Studios. MS has different versioning for Visual Studio product, for
Visual C++ product and for CL compiler itself.

Also - can you name some template-related C++ features absent in VC6 aka VS98
aka CL 12.x?

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
ma***@storagecr aft.com
http://www.storagecraft.com

[Jonathan Mcdougall]

Maxim S. Shatskih wrote:

Prior to Visual C++ 7.0

Is it Visual Studio 2003?

7.0 is .NET 2002 and 7.1 is .NET 2003.
Also - can you name some template-related C++ features absent in VC6 aka VS98
aka CL 12.x?

I am not sure whether these features appeared in 7.0 or 7.1, but here
some I can think of right now:

.. partial specialization
.. argument-dependent lookup (ADL)
.. template template parameters
.. out-of-class member template definitions

Plus, many bugs ("internal compiler error") have been fixed and
conformance to the standard is quite correct. It compiles Boost and
Loki with no problem, while 6.0 was barely able to compile its own
standard library.
Jonathan

[CBFalconer]

"Maxim S. Shatskih" wrote:

I am glad to hear this -- because it would be wrong.
'w' and 'b' are both standard C, as is "wb".
I saw Linux failing fopen() if "wb" is specified, so I considered
this to be Microsoftism.

From N869:

7.19.5.3 The fopen function

Synopsis

[#1]

#include <stdio.h>
FILE *fopen(const char * filename,
const char * mode);

Description

[#2] The fopen function opens the file whose name is the
string pointed to by filename, and associates a stream with
it.

[#3] The argument mode points to a string. If the string is
one of the following, the file is open in the indicated
mode. Otherwise, the behavior is undefined.214)

r open text file for reading
w truncate to zero length or create text file for
writing
a append; open or create text file for writing at
end-of-file
rb open binary file for reading
wb truncate to zero length or create binary file for
writing
ab append; open or create binary file for writing at
end-of-file
r+ open text file for update (reading and writing)
w+ truncate to zero length or create text file for
update
a+ append; open or create text file for update,
writing at end-of-file
r+b or rb+ open binary file for update (reading and writing)
w+b or wb+ truncate to zero length or create binary file
for update
a+b or ab+ append; open or create binary file for update,
writing at end-of-file

--
Chuck F (cb********@yah oo.com) (cb********@wor ldnet.att.net)
Available for consulting/temporary embedded and systems.
<http://cbfalconer.home .att.net> USE worldnet address!

[Dave Thompson]

On 8 Mar 2005 23:08:10 GMT, ro******@ibd.nr c-cnrc.gc.ca (Walter
Roberson) wrote:
<snip>

If you are trying to find a language that says, "It's okay to
redefine the system library routines," then the only one I can think
of at the moment is Forth. LISP and Scheme too maybe.

Actually in Forth everything is a 'word' (dictionary entry) including
things that other languages (including C) consider 'primitive' like
add, dereference, IF-ELSE, etc., and you can redefine any word.
Similarly in LISP everything except for a few syntactic forms, and
AIUI in Scheme everything period, is just a named function, and (all
such) can be redefined.

Fortran allows you to (re)use the names of 'intrinsic' (library)
routines for your own subprograms if you explicitly declare them
EXTERNAL as opposed to INTRINSIC, and PL/I similarly if you declare
them ENTRY rather than BUILTIN, but this can not affect things like +
and DO. Fortran>=90, like C++, allows you to overload for user-defined
types the builtin computational operators and assignment (which unlike
C++ is not just an operator) but you cannot override the standard
meanings for builtin/basic types. F9X also allows you to create
entirely new operators, which you must of course define for all cases
(types) you want to handle.

Ada has hierarchical namespaces and you can use in your own
namespace(s) the same names that the standard routines use in the
standard namespaces, but this does not replace or even completely hide
the standard ones.
- David.Thompson1 at worldnet.att.ne t