From: Alex Vinokur <alexander.vinokur@telrad.co.il>
To: help-gcc@gnu.org
Subject: Re: how to declare dynamic 2-dimensional array in C++?
Date: Sun, 02 Jan 2000 21:35:00 -0000 [thread overview]
Message-ID: <84pbp4$j4t$1@nnrp1.deja.com> (raw)
In-Reply-To: <386fac89@eeyore.callnetuk.com>
In article <386fac89@eeyore.callnetuk.com>,
"Chris Newton" <not@all.likely> wrote:
> Alex Vinokur <alexander.vinokur@telrad.co.il> wrote...
> > The following construction is valid
in gcc/g++ compiler (See my original message).
>
> [snip]
>
> >
> >
> > int main ()
> > {
> > foo (10, 200, 3000);
> > return 0;
> > }
>
> Sorry, but no, that's not valid. Please see the C++ Standard, sections
> 8.3.4 (on arrays) and 5.19 (on the definition of an integral constant
> expression).
>
> Cheers,
> Chris
>
>
GNU compiler (gcc/g++/egcs) contains several advanced non-standard
features. For instance,
1. void foo (int s1, int s2, int s3)
{
char aaa [s1] [s2] [s3];
}
That code is legal in g++.
2. switch (value)
{
case 1 :
break;
case 100 ... 200 : // Legal in g++
break;
}
3. __PRETTY_FUNCTION__
--FUNCTION__
(Does anybody know something else?)
(I think) All these feature are very useful.
Of course we have to realize that they are non-standard.
By the way, is it worth standardizing them?
Alex
Sent via Deja.com http://www.deja.com/
Before you buy.
WARNING: multiple messages have this Message-ID
From: Alex Vinokur <alexander.vinokur@telrad.co.il>
To: help-gcc@gnu.org
Subject: Re: how to declare dynamic 2-dimensional array in C++?
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <84pbp4$j4t$1@nnrp1.deja.com> (raw)
Message-ID: <20000401000000.9UjZ4ba4NzbRDLoR0tmhklLnHfXcGV1Ae5XNsjBVEZ0@z> (raw)
In-Reply-To: <386fac89@eeyore.callnetuk.com>
In article <386fac89@eeyore.callnetuk.com>,
"Chris Newton" <not@all.likely> wrote:
> Alex Vinokur <alexander.vinokur@telrad.co.il> wrote...
> > The following construction is valid
in gcc/g++ compiler (See my original message).
>
> [snip]
>
> >
> >
> > int main ()
> > {
> > foo (10, 200, 3000);
> > return 0;
> > }
>
> Sorry, but no, that's not valid. Please see the C++ Standard, sections
> 8.3.4 (on arrays) and 5.19 (on the definition of an integral constant
> expression).
>
> Cheers,
> Chris
>
>
GNU compiler (gcc/g++/egcs) contains several advanced non-standard
features. For instance,
1. void foo (int s1, int s2, int s3)
{
char aaa [s1] [s2] [s3];
}
That code is legal in g++.
2. switch (value)
{
case 1 :
break;
case 100 ... 200 : // Legal in g++
break;
}
3. __PRETTY_FUNCTION__
--FUNCTION__
(Does anybody know something else?)
(I think) All these feature are very useful.
Of course we have to realize that they are non-standard.
By the way, is it worth standardizing them?
Alex
Sent via Deja.com http://www.deja.com/
Before you buy.
next parent reply other threads:[~2000-01-02 21:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <386da233.0@news.tm.net.my>
[not found] ` <84n59m$daj$1@nnrp1.deja.com>
[not found] ` <386fac89@eeyore.callnetuk.com>
2000-01-02 21:35 ` Alex Vinokur [this message]
2000-01-03 3:55 ` Johnny Favorite (it means "Writhing Tentacle of Death")
2000-01-03 10:16 ` Martin Ambuhl
2000-01-03 11:04 ` Greg Comeau
2000-04-01 0:00 ` Greg Comeau
2000-01-04 4:24 ` Johnny Favorite (it means "Writhing Tentacle of Death")
2000-04-01 0:00 ` Johnny Favorite (it means "Writhing Tentacle of Death")
2000-04-01 0:00 ` Martin Ambuhl
2000-01-04 5:55 ` __PRETTY_FUNCTION__, functions and templates Alex Vinokur
2000-04-01 0:00 ` Alex Vinokur
2000-04-01 0:00 ` how to declare dynamic 2-dimensional array in C++? Johnny Favorite (it means "Writhing Tentacle of Death")
2000-04-01 0:00 ` Alex Vinokur
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='84pbp4$j4t$1@nnrp1.deja.com' \
--to=alexander.vinokur@telrad.co.il \
--cc=help-gcc@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).