Re: Array size limits

From: CBFalconer (cbfalconer_at_yahoo.com)
Date: 09/01/04 

Date: Wed, 01 Sep 2004 19:01:24 GMT

*** Evil top-posting fixed ***

grv575 wrote:
> Keith Thompson <kst-u@mib.org> wrote
>> "Wei Li" <liwei_guard-pub@yahoo.com> writes:
>>
 ... snip ...
>
>>> I don't know how ANSI C says. But the stacksize of a program
>>> in runtime is limited by Opterating System. So that C compiler
>>> always doesn't give out an compile time error.
>>>
>>> If you are on Linux, you can use "limit" command to show the
>>> limits and use "limit stacksize 1000000" to change them. I think
>>> your program will work OK
>>
>> Wei Li: Please don't top-post.
>>
>> Top-posting means writing your new material first, followed by the
>> quoted article to which you're responding. It makes it difficult
>> to follow the discussion, especially when (almost) everyone else
>> bottom-posts, as I'm doing there. (You should also trim anything
>> that's not relevant to your response, though in this case the
>> previous article was short enough that quoting the whole thing is
>> probably ok.)
>
> Please use google groups to read news. It syntax highlights
> everything so threads aren't difficult to follow either way. Btw,
> I prefer "topposting" since you don't have to scroll past what's
> already been said in the thread.

In comp.lang.c you are requested to bottom post (or interleave)
with proper snipping of irrelevant material. If you don't you may
well be plonked, which means that many people will never see any
of your posts. This tends to be non-productive.

Google groups is one of the slowest and awkwardest ways to read
news. Among other things many items never appear there, due to
foolish use of X-noarchive, and things that do appear have a delay
of several hours. On the other hand its archive is invaluable,
and it provides access for people without a newsreader (or behind
firewalls that prevent newserver access). This generally includes
library access, for example.
>
> I'm really surprised though that noone has pointed out so far that
> most compilers will have some kind of flag or directive to allow a
> larger stack size which is the most likely wall you're running in to
> (all this talk of standards and no real solutions).
 
Such compiler or system specific things are not portable, and are
thus off-topic here. Thus the proper reference is to a group
dealing with the specific system. There is not necessarily any
such thing as a stack. 

-- 
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?

Relevant Pages

  • Re: Prototype - Good/Bad/Why?
    ... rather than Usenet. ... This is not to say that Google groups interface cannot show Usenet in its ... References header that describes its context in the tree of the thread by ... the message that the current message is responding to at the end. ...
    (comp.lang.javascript)
  • Re: Prototype - Good/Bad/Why?
    ... rather than Usenet. ... This is not to say that Google groups interface cannot show Usenet in its ... References header that describes its context in the tree of the thread by ... the message that the current message is responding to at the end. ...
    (comp.lang.javascript)
  • Re: FTP Problem (was FTP Issue)
    ... responding in future. ... subscribe to receiving the Google Groups digest. ... explanation of the Dynalloc return codes. ... Search the archives at http://bama.ua.edu/archives/ibm-main.html ...
    (bit.listserv.ibm-main)
  • Re: Saints Unnamed on 6-20-06 at 1:00 P.M.
    ... Newcomer's FAQ ... Some people might complain that you spammed -- you didn't, technically, ... The custom here is to quote the part of the message you're responding to ... Google Groups doesn't make it obvious how to do this, ...
    (rec.arts.sf.composition)
  • Re: Array size limits
    ... >> limited by Opterating System. ... >> compile time error. ... > quoted article to which you're responding. ...
    (comp.lang.c)