Console width and height, MS Visual C++

[Piotrek]

<<If this message is duplicated, please ignore the previous one, I had
some connection problems>>

Hi,
Could you please tell me how to check width and height of Windows
console program (cmd.exe)in MS Visual C++ 2005 Express Edition?

The goal is something like "more" command. So I print n lines of a file,
where n is number of rows, program waits for a key and prints further
part of that file, etc.

I've found description of "gettextinfo" function [void
gettextinfo(struct text_info *Info); ] in "conio.h". But this is Borland
implementation. I think there's no such function in MS C++.

What's more I want it to be a clean C program, without C++ objects.

Thank you!

--
Piotrek

[Walter Roberson]

In article <f1**********@news.task.gda.pl>,
Piotrek <no*****@noreply.comwrote:

>Could you please tell me how to check width and height of Windows
console program (cmd.exe)in MS Visual C++ 2005 Express Edition?

>What's more I want it to be a clean C program, without C++ objects.

There is no way to do what you ask in Standard C. You require
system-specific extensions, which you will need to ask about in
a newsgroup that specializes in your operating system.
--
I was very young in those days, but I was also rather dim.
-- Christopher Priest

[jacob navia]

Piotrek a écrit :

<<If this message is duplicated, please ignore the previous one, I had
some connection problems>>

Hi,
Could you please tell me how to check width and height of Windows
console program (cmd.exe)in MS Visual C++ 2005 Express Edition?

The goal is something like "more" command. So I print n lines of a file,
where n is number of rows, program waits for a key and prints further
part of that file, etc.

I've found description of "gettextinfo" function [void
gettextinfo(struct text_info *Info); ] in "conio.h". But this is Borland
implementation. I think there's no such function in MS C++.

What's more I want it to be a clean C program, without C++ objects.

Thank you!

You should look at the GetConsoleXXX API. For instance, a promising
start would be

BOOL GetConsoleScreenBufferInfo(
HANDLE hConsoleOutput,
PCONSOLE_SCREEN_BUFFER_INFO lpConsoleScreenBufferInfo
);

Parameters
hConsoleOutput
[in] Handle to a console screen buffer. The handle must have the
GENERIC_READ access right. For more information, see Console Buffer
Security and Access Rights.
lpConsoleScreenBufferInfo
[out] Pointer to a CONSOLE_SCREEN_BUFFER_INFO structure that receives
the console screen buffer information.
Return Values
If the function succeeds, the return value is nonzero.

If the function fails, the return value is zero. To get extended error
information, call GetLastError.

Remarks
The rectangle returned in the srWindow member of the
CONSOLE_SCREEN_BUFFER_INFO structure can be modified and then passed to
the SetConsoleWindowInfo function to scroll the console screen buffer in
the window, to change the size of the window, or both.

All coordinates returned in the CONSOLE_SCREEN_BUFFER_INFO structure are
in character-cell coordinates, where the origin (0, 0) is at the
upper-left corner of the console screen buffer.

[Walter Roberson]

In article <46***********************@news.orange.fr>,
jacob navia <ja***@jacob.remcomp.frwrote:

>Piotrek a écrit :

>Could you please tell me how to check width and height of Windows
console program (cmd.exe)in MS Visual C++ 2005 Express Edition?

>You should look at the GetConsoleXXX API. For instance, a promising
start would be

>BOOL GetConsoleScreenBufferInfo(
HANDLE hConsoleOutput,
PCONSOLE_SCREEN_BUFFER_INFO lpConsoleScreenBufferInfo
);

Jacob, I must have overlooked something in the C89 or C99 standards;
could you kindly point out the sections in which
GetConsoleScreenBufferInfo() is defined? My memory must be particularily
crappy today, as I also seem to have trouble recalling the
Standard definition of BOOL, HANDLE, and PCONSOLE_SCREEN_BUFFER_INFO.
Which standard header file are those in?

The original poster expressed a particular interest in performing
this function in "clean C", and my memory can't seem to reconcile
your answer with clean C.
--
All is vanity. -- Ecclesiastes

[jacob navia]

Walter Roberson a écrit :

In article <46***********************@news.orange.fr>,
jacob navia <ja***@jacob.remcomp.frwrote:

>>Piotrek a écrit :

>>>Could you please tell me how to check width and height of Windows
console program (cmd.exe)in MS Visual C++ 2005 Express Edition?

>>You should look at the GetConsoleXXX API. For instance, a promising
start would be

>>BOOL GetConsoleScreenBufferInfo(
HANDLE hConsoleOutput,
PCONSOLE_SCREEN_BUFFER_INFO lpConsoleScreenBufferInfo
);

Jacob, I must have overlooked something in the C89 or C99 standards;
could you kindly point out the sections in which
GetConsoleScreenBufferInfo() is defined? My memory must be particularily
crappy today, as I also seem to have trouble recalling the
Standard definition of BOOL, HANDLE, and PCONSOLE_SCREEN_BUFFER_INFO.
Which standard header file are those in?

The original poster expressed a particular interest in performing
this function in "clean C", and my memory can't seem to reconcile
your answer with clean C.

In the TITLE of the poster message was specified "MS VISUAL C++".

HANDLE is a windows standard for a void * in most cases. Assuming
32 bits windows we could have written:
int GetConsoleScreenBufferInfo(void *,CONSOLE_SCREEN_BUFFER_INFO *);
The CONSOLE_SCREEN_BUFFER is defined elsewhere.

This is as clean as C gets() ... :-)

jacob

[Walter Roberson]

In article <46**********************@news.orange.fr>,
jacob navia <ja***@jacob.remcomp.frwrote:

>Walter Roberson a écrit :

>In article <46***********************@news.orange.fr>,
jacob navia <ja***@jacob.remcomp.frwrote:

>>>Piotrek a écrit :

>>>>Could you please tell me how to check width and height of Windows
console program (cmd.exe)in MS Visual C++ 2005 Express Edition?

>>>BOOL GetConsoleScreenBufferInfo(
HANDLE hConsoleOutput,
PCONSOLE_SCREEN_BUFFER_INFO lpConsoleScreenBufferInfo
);

>Jacob, I must have overlooked something in the C89 or C99 standards;
could you kindly point out the sections in which
GetConsoleScreenBufferInfo() is defined?

>In the TITLE of the poster message was specified "MS VISUAL C++".

>HANDLE is a windows standard for a void * in most cases. Assuming
32 bits windows we could have written:
int GetConsoleScreenBufferInfo(void *,CONSOLE_SCREEN_BUFFER_INFO *);
The CONSOLE_SCREEN_BUFFER is defined elsewhere.

Defined elsewhere? In a different section of the C89 or C99 standards??

I seem to be having difficulty understanding your answer. A
poster came here and specifically asked for a C response, but
your reference to "32 bits windows" is sounding dangerously
like you answered in terms of a system-specific interface
without noting that the interface was system specific, and without
noting that the response was off-topic. Such responses lead
to confusion about what is part of standard C and what is
part of an OS (and not even covered by -any- official standard.)

--
I was very young in those days, but I was also rather dim.
-- Christopher Priest

[Malcolm McLean]

"jacob navia" <ja***@jacob.remcomp.frwrote in message
news:46***********************@news.orange.fr...

Piotrek a écrit :

><<If this message is duplicated, please ignore the previous one, I had
some connection problems>>

Hi,
Could you please tell me how to check width and height of Windows console
program (cmd.exe)in MS Visual C++ 2005 Express Edition?

The goal is something like "more" command. So I print n lines of a file,
where n is number of rows, program waits for a key and prints further
part of that file, etc.

I've found description of "gettextinfo" function [void gettextinfo(struct
text_info *Info); ] in "conio.h". But this is Borland implementation. I
think there's no such function in MS C++.

What's more I want it to be a clean C program, without C++ objects.

Thank you!

You should look at the GetConsoleXXX API. For instance, a promising
start would be

BOOL GetConsoleScreenBufferInfo(
HANDLE hConsoleOutput,
PCONSOLE_SCREEN_BUFFER_INFO lpConsoleScreenBufferInfo
);

I used to program DOS in the olden days. But now I really can't remember all
these sorts of details. So I wouldn't like to say whether your information
is correct or not.
That's the problem with not directing these posts to somewhere more
suitable. The other problem is that if we dealt with every library on every
platform the volume of posts would become unmanageable.

[Richard Heathfield]

Malcolm McLean said:

>
"jacob navia" <ja***@jacob.remcomp.frwrote in message
news:46***********************@news.orange.fr...

>>
You should look at the GetConsoleXXX API. For instance, a promising
start would be

BOOL GetConsoleScreenBufferInfo(
HANDLE hConsoleOutput,
PCONSOLE_SCREEN_BUFFER_INFO lpConsoleScreenBufferInfo
);

I used to program DOS in the olden days. But now I really can't
remember all these sorts of details. So I wouldn't like to say whether
your information is correct or not.

Well, it isn't a DOS answer. It's a Win32 API answer. Of course, whether
it is a correct answer for Win32 API is a matter more properly directed
to comp.os.ms-windows.programmer.win32

That's the problem with not directing these posts to somewhere more
suitable. The other problem is that if we dealt with every library on
every platform the volume of posts would become unmanageable.

Right.

--
Richard Heathfield
"Usenet is a strange place" - dmr 29/7/1999
http://www.cpax.org.uk
email: rjh at the above domain, - www.

[Martin Ambuhl]

Piotrek wrote:

<<If this message is duplicated, please ignore the previous one, I had
some connection problems>>

Hi,
Could you please tell me how to check width and height of Windows
console program (cmd.exe)in MS Visual C++ 2005 Express Edition?

With something that is specific to that implementation and that
operating system, and that is completely off-topic in comp.lang.c.
There are almost as many newsgroups for Windows and MSVC as there are
instances of bloat in Windows. Why would you not ask there, where the
experts in that platform live?

>
The goal is something like "more" command. So I print n lines of a file,
where n is number of rows, program waits for a key and prints further
part of that file, etc.

I've found description of "gettextinfo" function [void
gettextinfo(struct text_info *Info); ] in "conio.h". But this is Borland
implementation. I think there's no such function in MS C++.

There are no such things as "gettextinfo" "struct text_info", or
"conio.h" in C or C++. If there were, you would not be needed to ask
about specific implementations. Since you _are_ asking about a specific
implementation, it makes sense to ask in a newsgroup for that
implementation.

[Richard]

Martin Ambuhl <ma*****@earthlink.netwrites:

Piotrek wrote:

><<If this message is duplicated, please ignore the previous one, I
had some connection problems>>

Hi,
Could you please tell me how to check width and height of Windows
console program (cmd.exe)in MS Visual C++ 2005 Express Edition?

With something that is specific to that implementation and that
operating system, and that is completely off-topic in
comp.lang.c. There are almost as many newsgroups for Windows and MSVC
as there are instances of bloat in Windows. Why would you not ask
there, where the experts in that platform live?

>>
The goal is something like "more" command. So I print n lines of a
file, where n is number of rows, program waits for a key and prints
further part of that file, etc.

I've found description of "gettextinfo" function [void
gettextinfo(struct text_info *Info); ] in "conio.h". But this is
Borland implementation. I think there's no such function in MS C++.

There are no such things as "gettextinfo" "struct text_info", or
"conio.h" in C or C++. If there were, you would not be needed to ask
about specific implementations. Since you _are_ asking about a
specific implementation, it makes sense to ask in a newsgroup for that
implementation.

How many ways do you need to say "off topic"? Kicking a man when he is
down is considered pretty "off topic" in civilised circles.

[Richard]

ro******@ibd.nrc-cnrc.gc.ca (Walter Roberson) writes:

In article <46**********************@news.orange.fr>,
jacob navia <ja***@jacob.remcomp.frwrote:

>>Walter Roberson a écrit :

>>In article <46***********************@news.orange.fr>,
jacob navia <ja***@jacob.remcomp.frwrote:

>>>>Piotrek a écrit :

>>>>>Could you please tell me how to check width and height of Windows
>console program (cmd.exe)in MS Visual C++ 2005 Express Edition?

>>>>BOOL GetConsoleScreenBufferInfo(
HANDLE hConsoleOutput,
PCONSOLE_SCREEN_BUFFER_INFO lpConsoleScreenBufferInfo
);

>>Jacob, I must have overlooked something in the C89 or C99 standards;
could you kindly point out the sections in which
GetConsoleScreenBufferInfo() is defined?

>>In the TITLE of the poster message was specified "MS VISUAL C++".

>>HANDLE is a windows standard for a void * in most cases. Assuming
32 bits windows we could have written:
int GetConsoleScreenBufferInfo(void *,CONSOLE_SCREEN_BUFFER_INFO *);
The CONSOLE_SCREEN_BUFFER is defined elsewhere.

Defined elsewhere? In a different section of the C89 or C99
standards??

You made your point.

But isn't there a "std" C group too where you would be better off
lecturing repeatedly?

>
I seem to be having difficulty understanding your answer. A
poster came here and specifically asked for a C response, but
your reference to "32 bits windows" is sounding dangerously
like you answered in terms of a system-specific interface
without noting that the interface was system specific, and without
noting that the response was off-topic. Such responses lead
to confusion about what is part of standard C and what is
part of an OS (and not even covered by -any- official standard.)

[Richard]

ro******@ibd.nrc-cnrc.gc.ca (Walter Roberson) writes:

In article <f1**********@news.task.gda.pl>,
Piotrek <no*****@noreply.comwrote:

>>Could you please tell me how to check width and height of Windows
console program (cmd.exe)in MS Visual C++ 2005 Express Edition?

>>What's more I want it to be a clean C program, without C++ objects.

There is no way to do what you ask in Standard C. You require
system-specific extensions, which you will need to ask about in
a newsgroup that specializes in your operating system.

You felt the need to post 3 replies in this thread. All saying the same
thing. When it had already been done by another poster. Well done for
wasting everyones time.

[Keith Thompson]

jacob navia <ja***@jacob.remcomp.frwrites:

Walter Roberson a écrit :

>In article <46***********************@news.orange.fr>,
jacob navia <ja***@jacob.remcomp.frwrote:

>>>Piotrek a écrit :

Could you please tell me how to check width and height of Windows
console program (cmd.exe)in MS Visual C++ 2005 Express Edition?

>>>You should look at the GetConsoleXXX API. For instance, a promising
start would be

>>>BOOL GetConsoleScreenBufferInfo(
HANDLE hConsoleOutput,
PCONSOLE_SCREEN_BUFFER_INFO lpConsoleScreenBufferInfo
);

Jacob, I must have overlooked something in the C89 or C99 standards;
could you kindly point out the sections in which
GetConsoleScreenBufferInfo() is defined?

[...]

In the TITLE of the poster message was specified "MS VISUAL C++".

[...]

The "Newsgroups": header says "comp.lang.c". As you know perfectly
well, the OP's question cannot be completely answered in the context
of this newsgroup. Providing system-specific details here, where they
cannot necessarily be checked by other participants, clutters this
newsgroup and is a disservice to the original poster.

I suspect that comp.os.ms-windows.programmer.win32 is full of people
who know all about this stuff. Why did you not bother to mention that
newsgroup in your response? (One might suspect that you're trying to
show off your knowledge of Windows programming in a forum with minimal
competition.)

--
Keith Thompson (The_Other_Keith) ks***@mib.org <http://www.ghoti.net/~kst>
San Diego Supercomputer Center <* <http://users.sdsc.edu/~kst>
"We must do something. This is something. Therefore, we must do this."
-- Antony Jay and Jonathan Lynn, "Yes Minister"

[Keith Thompson]

Piotrek <no*****@noreply.comwrites:
[...]

Could you please tell me how to check width and height of Windows
console program (cmd.exe)in MS Visual C++ 2005 Express Edition?

[...]

Sorry, we can't. Standard C, which is what we discuss here, has no
facilities for this kind of thing.

Section 19 of the comp.lang.c FAQ, <http://www.c-faq.com/>, might be
helpful, particularly question 19.4, though the information there
seems to be mostly specific to Unix and, to a lesser extent, MS-DOS
(it's fairly old).

You can probably get better information in
comp.os.ms-windows.programmer.win32. If that's not the correct forum,
they can probably direct you to a better one Before posting there, see
if you can find a FAQ list for that newsgroup; your question may
already have been answered.

--
Keith Thompson (The_Other_Keith) ks***@mib.org <http://www.ghoti.net/~kst>
San Diego Supercomputer Center <* <http://users.sdsc.edu/~kst>
"We must do something. This is something. Therefore, we must do this."
-- Antony Jay and Jonathan Lynn, "Yes Minister"

[Walter Roberson]

In article <87************@gmail.com>, Richard <rg****@gmail.comwrote:

>ro******@ibd.nrc-cnrc.gc.ca (Walter Roberson) writes:

>There is no way to do what you ask in Standard C. You require
system-specific extensions, which you will need to ask about in
a newsgroup that specializes in your operating system.

>You felt the need to post 3 replies in this thread. All saying the same
thing. When it had already been done by another poster. Well done for
wasting everyones time.

You should check out the timestamps before making such a claim.
My posting that you were replying to as if it were a duplication of
effort, was in fact the first reply, approximately 10 minutes before
Jacob's reply.

Well done for wasting everyones time.

You could always put me in your kill file if you find my
contributions unsatisfactory.

--
Programming is what happens while you're busy making other plans.

[Richard Heathfield]

Richard said:

ro******@ibd.nrc-cnrc.gc.ca (Walter Roberson) writes:

>In article <46**********************@news.orange.fr>,
jacob navia <ja***@jacob.remcomp.frwrote:

>>>The CONSOLE_SCREEN_BUFFER is defined elsewhere.

Defined elsewhere? In a different section of the C89 or C99
standards??

You made your point.

But isn't there a "std" C group too where you would be better off
lecturing repeatedly?

comp.std.c is for discussions about the document that defines the C
language. It's all about defect reports, clarifications of wording, the
mythical C0x revision, and so on.

comp.lang.c, on the other hand, is for discussions about the C language.

Windows programming is adequately covered by
comp.os.ms-windows.programmer.win32

--
Richard Heathfield
"Usenet is a strange place" - dmr 29/7/1999
http://www.cpax.org.uk
email: rjh at the above domain, - www.

[Keith Thompson]

Richard <rg****@gmail.comwrites:

ro******@ibd.nrc-cnrc.gc.ca (Walter Roberson) writes:

>In article <46**********************@news.orange.fr>,
jacob navia <ja***@jacob.remcomp.frwrote:

[...]

>>>The CONSOLE_SCREEN_BUFFER is defined elsewhere.

Defined elsewhere? In a different section of the C89 or C99
standards??

You made your point.

But isn't there a "std" C group too where you would be better off
lecturing repeatedly?

[...]

No. comp.std.c is for discussion of the C standard; comp.lang.c is
for discussion of the language defined by that standard (and earlier
incarnations of it). OS-specific details are off-topic in either
group.

--
Keith Thompson (The_Other_Keith) ks***@mib.org <http://www.ghoti.net/~kst>
San Diego Supercomputer Center <* <http://users.sdsc.edu/~kst>
"We must do something. This is something. Therefore, we must do this."
-- Antony Jay and Jonathan Lynn, "Yes Minister"

[CBFalconer]

Richard wrote:

Martin Ambuhl <ma*****@earthlink.netwrites:

>Piotrek wrote:

>>Could you please tell me how to check width and height of Windows
console program (cmd.exe)in MS Visual C++ 2005 Express Edition?

.... snip ...

>>
There are no such things as "gettextinfo" "struct text_info", or
"conio.h" in C or C++. If there were, you would not be needed to
ask about specific implementations. Since you _are_ asking about
a specific implementation, it makes sense to ask in a newsgroup
for that implementation.

How many ways do you need to say "off topic"? Kicking a man when
he is down is considered pretty "off topic" in civilised circles.

He didn't kick anybody, just gave him a polite answer with info
about where to go.

--
<http://www.cs.auckland.ac.nz/~pgut001/pubs/vista_cost.txt>
<http://www.securityfocus.com/columnists/423>
<http://www.aaxnet.com/editor/edit043.html>
<http://kadaitcha.cx/vista/dogsbreakfast/index.html>
cbfalconer at maineline dot net

--
Posted via a free Usenet account from http://www.teranews.com

[Jack Klein]

On Mon, 07 May 2007 22:55:13 +0200, Richard <rg****@gmail.comwrote
in comp.lang.c:

Martin Ambuhl <ma*****@earthlink.netwrites:

[snip]

How many ways do you need to say "off topic"? Kicking a man when he is
down is considered pretty "off topic" in civilised circles.

Fortunately, plonking a jerk, whether he is up or down, is considered
useful.

*plonk*

--
Jack Klein
Home: http://JK-Technology.Com
FAQs for
comp.lang.c http://c-faq.com/
comp.lang.c++ http://www.parashift.com/c++-faq-lite/
alt.comp.lang.learn.c-c++
http://www.club.cc.cmu.edu/~ajo/docs/FAQ-acllc.html

[jacob navia]

Richard Heathfield a écrit :

comp.lang.c, on the other hand, is for discussions about the C language.

This is just your opinion.
This group has no chart.

[Walter Roberson]

In article <46***********************@news.orange.fr>,
jacob navia <ja***@jacob.remcomp.frwrote:

>Richard Heathfield a écrit :

>comp.lang.c, on the other hand, is for discussions about the C language.

>This is just your opinion.
This group has no chart.

If we went through the bother of filing an official charter,
would you post any differently than you do now?

--
Okay, buzzwords only. Two syllables, tops. -- Laurie Anderson

[Richard Heathfield]

jacob navia said:

Richard Heathfield a écrit :

>comp.lang.c, on the other hand, is for discussions about the C
language.

This is just your opinion.

Not so. It is the opinion of a great many people who contribute
regularly to this group.

This group has no chart.

Right. It doesn't have a charter, either. The most it has is a control
file, which reads something like "discussions about C". Note the
absence of statements such as "discussions about Win32 console I/O".

Oh, I nearly forgot - it also has a *name*.

comp - one of the "big 8", and a quick look through the comp.* hierarchy
will convince any reasonable person that it is short for "computers" or
"computing" or "computation" or some other derivative of the word
"compute".

lang - short for "languages", as another quick look through the
hierarchy will confirm to any reasonable person.

c - short for C. One of those funky recursive acronyms.

So there is plenty of justification for treating this newsgroup as a
group for discussing the COMPuter LANGuage called C.

I see no justification for discussing other subjects, such as
platform-specific I/O libraries.

And as if that were not enough, the existence of groups such as
comp.os.ms-windows.programmer.win32 shows that there is no shortage of
groups for platform-specific discussions.

--
Richard Heathfield
"Usenet is a strange place" - dmr 29/7/1999
http://www.cpax.org.uk
email: rjh at the above domain, - www.

[=?ISO-8859-1?Q?Bj=F8rn_Augestad?=]

Richard Heathfield wrote:

jacob navia said:

>Richard Heathfield a écrit :

>>comp.lang.c, on the other hand, is for discussions about the C
language.

This is just your opinion.

Not so. It is the opinion of a great many people who contribute
regularly to this group.

>This group has no chart.

Right. It doesn't have a charter, either. The most it has is a control
file, which reads something like "discussions about C".

Actually, it has more than just a control file. This may be the c.l.c.
equivalent of the dead sea scrolls, but once upon a time a wise man
named Jerry Schwarz created net.lang.c (known today as comp.lang.c) and
wrote this as the first post to the group:

My suggestion for a "C" newsgroup met with support and no
opposition so net.lang.c (note lower case) has been created.

It's purpose is to carry on discussion of C programming and
the C programming language. Appropriate topics are

Queries on how to write something in C
Queries about why some C code behaves the way it does
Suggestions for C modifications or extensions
C coding "tricks"
Compiler bugs
Availability of compilers
etc.

Jerry Schwarz
BTL -- Murray Hill
harpo!eagle!jerry

http://groups.google.com/group/net.n...2db040d8e0ba75
HAND
Bjørn

[snip]

[jacob navia]

Bjørn Augestad wrote:

Richard Heathfield wrote:

>jacob navia said:

>>Richard Heathfield a écrit :

comp.lang.c, on the other hand, is for discussions about the C
language.

This is just your opinion.

Not so. It is the opinion of a great many people who contribute
regularly to this group.

>>This group has no chart.

Right. It doesn't have a charter, either. The most it has is a control
file, which reads something like "discussions about C".

Actually, it has more than just a control file. This may be the c.l.c.
equivalent of the dead sea scrolls, but once upon a time a wise man
named Jerry Schwarz created net.lang.c (known today as comp.lang.c) and
wrote this as the first post to the group:

>My suggestion for a "C" newsgroup met with support and no
opposition so net.lang.c (note lower case) has been created.

It's purpose is to carry on discussion of C programming and
the C programming language. Appropriate topics are

Queries on how to write something in C
Queries about why some C code behaves the way it does
Suggestions for C modifications or extensions

How times have changed.

In that times apparently, this ossification, and sclerosis of the people
here wasn't yet there. This must be in the eighties something probably.

Do you have the exact date of this message?

Thanks for posting this message.

> C coding "tricks"
Compiler bugs
Availability of compilers
etc.

Jerry Schwarz
BTL -- Murray Hill
harpo!eagle!jerry

http://groups.google.com/group/net.n...2db040d8e0ba75

HAND
Bjørn

[snip]

[Walter Roberson]

In article <46**********************@news.orange.fr>,
jacob navia <ja***@jacob.remcomp.frwrote:

>Bjørn Augestad wrote:

>>It's purpose is to carry on discussion of C programming and
the C programming language. Appropriate topics are

>> Queries on how to write something in C
Queries about why some C code behaves the way it does
Suggestions for C modifications or extensions

>How times have changed.

>In that times apparently, this ossification, and sclerosis of the people
here wasn't yet there. This must be in the eighties something probably.

When net.lang.c was created, there weren't very many newsgroups.
As new technologies were introduced, and as interest in the topics
increased, it became necessary to create additional newsgroups more
specialized, as otherwise there was risk of drowning the core discussions.

Imagine if you took all of the SourceForge project discussions
for projects implemented in C, and dumped them all into this one
newsgroup, comp.lang.c. You wouldn't be able to get much done here:
the "noise" would be too high.

net.lang.c was created at a time when there was only a bit of
public access to newsgroups, when the Internet was still largely
military and academic and research, before even dialup ISPs were common.
It was never designed to handle the flood of information from
the days when 24/7 high speed access is common in homes.
--
If you lie to the compiler, it will get its revenge. -- Henry Spencer

[Mark McIntyre]

On Mon, 07 May 2007 20:19:19 +0200, in comp.lang.c , jacob navia
<ja***@jacob.remcomp.frwrote:

>Piotrek a écrit :

><<If this message is duplicated, please ignore the previous one, I had
some connection problems>>

Hi,
Could you please tell me how to check width and height of Windows
console program (cmd.exe)in MS Visual C++ 2005 Express Edition?

You need to ask the Microsoft experts over in a microsoft group. The
topic here is the C language, and extensions such as the Win32API etc
are not discussed.

>You should look at the

completely offtopic stuff mentioned by Jacob.

Jacob, you _know_ this is offtopic here. Why do you persist in being
such a very rude and arrogant person?
--
Mark McIntyre

"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it."
--Brian Kernighan

[Mark McIntyre]

On Mon, 07 May 2007 22:58:32 +0200, in comp.lang.c , Richard
<rg****@gmail.comwrote:

>But isn't there a "std" C group too where you would be better off
lecturing repeatedly?

Oh, god, must we have this bloody argument _again_ ?

Please go and discover the topic of comp.std.c. Is it -really- so hard
to find out the topic of a group and stick to it? Hell, there are 50K
groups out there, no need to cram all human knowledge into just one of
them.

--
Mark McIntyre

"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it."
--Brian Kernighan

[Mark McIntyre]

On Tue, 08 May 2007 20:01:15 +0200, in comp.lang.c , jacob navia
<ja***@jacob.remcomp.frwrote:

>Richard Heathfield a écrit :

>comp.lang.c, on the other hand, is for discussions about the C language.

This is just your opinion.
This group has no chart.

(er missing)

We've had this debate too. Synopsis:

1) mention of the lack of charter is disingenuous and weaselly since
JN knows perfectly well that CLC predates such a system.

2) JN is apparently has no interest in obeying the rules of the
society he wants to be part of.

--
Mark McIntyre

"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it."
--Brian Kernighan

[Mark McIntyre]

On Mon, 07 May 2007 22:55:13 +0200, in comp.lang.c , Richard
<rg****@gmail.comwrote:

>
How many ways do you need to say "off topic"? Kicking a man when he is
down is considered pretty "off topic" in civilised circles.

On the other hand, telling someone he's breaking the conventions is
hardly uncivilised. If someone pees on your lunch, do you ignore them?
--
Mark McIntyre

"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it."
--Brian Kernighan