Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.c > #58343 > unrolled thread

New directions in C: Standard library input and output

Back to article view | Back to comp.lang.c

Contents

  New directions in C: Standard library input and output jacob navia <jacob@spamsink.net> - 2015-03-17 21:08 +0100
    Re: New directions in C: Standard library input and output Bartc <bc@freeuk.com> - 2015-03-17 20:18 +0000
    Re: New directions in C: Standard library input and output jacob navia <jacob@spamsink.net> - 2015-03-17 21:29 +0100
    Re: New directions in C: Standard library input and output Melzzzzz <mel@zzzzz.com> - 2015-03-18 01:00 +0100
      Re: New directions in C: Standard library input and output jacob navia <jacob@jacob.remcomp.fr> - 2015-03-18 09:00 +0100
        Re: New directions in C: Standard library input and output Melzzzzz <mel@zzzzz.com> - 2015-03-18 10:45 +0100

#58343 — New directions in C: Standard library input and output

1.9 Overloading shift operator
1.9.1 Motivation
As described in 1.3 the general advantages of operator overloading 
have been explained. The C standard library should also provide some 
structures which already have some operators overloaded in order to 
perform, for example, input and output.

For output the name outc should be used, for stderr the name errc and 
for input the name inc. There should also be definitions for newline, 
for example lend.

1.9.2 Syntax
outc << "This is a string on stdout" << lend;
errc << "And this on stderr" << lend;

[toc] | [next] | [standalone]

#58345

On 17/03/2015 20:08, jacob navia wrote:
> 1.9 Overloading shift operator

> 1.9.2 Syntax
> outc << "This is a string on stdout" << lend;
> errc << "And this on stderr" << lend;

So you /are/ reimplementing C++!

"<<" for output is one of its ugliest features and not one someone would 
voluntarily duplicate in another language.

-- 
Bartc

[toc] | [prev] | [next] | [standalone]

#58349

I am not the author of this rubbish

jacob

[toc] | [prev] | [next] | [standalone]

#58370

On Tue, 17 Mar 2015 21:08:06 +0100
jacob navia <jacob@spamsink.net> wrote:

> 1.9 Overloading shift operator
> 1.9.1 Motivation
> As described in 1.3 the general advantages of operator overloading 
> have been explained. The C standard library should also provide some 
> structures which already have some operators overloaded in order to 
> perform, for example, input and output.
> 
> For output the name outc should be used, for stderr the name errc and 
> for input the name inc. There should also be definitions for newline, 
> for example lend.
> 
> 1.9.2 Syntax
> outc << "This is a string on stdout" << lend;
> errc << "And this on stderr" << lend;
> 
> 

Heh, this really starts to look like c++ ;)

[toc] | [prev] | [next] | [standalone]

#58387

Le 18/03/2015 01:00, Melzzzzz a écrit :
>
> Heh, this really starts to look like c++ ;)
>

THIS IS A FORGED MESSAGE

There is nothing in the documentation of lcc-win, nor in the tutorial I 
wrote that makes any mention to this pile of ...

The objective of this guys is PRECISELY to make believe that I am 
reimplementing c++.

[toc] | [prev] | [next] | [standalone]

#58404

On Wed, 18 Mar 2015 09:00:26 +0100
jacob navia <jacob@jacob.remcomp.fr> wrote:

> Le 18/03/2015 01:00, Melzzzzz a écrit :
> >
> > Heh, this really starts to look like c++ ;)
> >
> 
> THIS IS A FORGED MESSAGE
> 
> There is nothing in the documentation of lcc-win, nor in the tutorial
> I wrote that makes any mention to this pile of ...
> 
> The objective of this guys is PRECISELY to make believe that I am 
> reimplementing c++.
> 
> 

Ah, ok. It was suspicious to me as well.

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.c

csiph-web