On 2005-12-07, at 16:26, Richard Guenther wrote:
On 12/7/05, Tommy Vercetti <[EMAIL PROTECTED]> wrote:
Hi there
We had funny issue here lately. Someone wanted to create table that
had 0 elements in C++, for instance this code:
This is a gcc extension. Try g++ -pedantic
This is
Hi there
We had funny issue here lately. Someone wanted to create table that
had 0 elements in C++, for instance this code:
int main()
{
char a[0];
char b[0];
a[0] = 1;
b[0] = 2;
return a[0] + b[0];
}
is perfectly ok for g++, it isn't for other compi
http://www.thedailywtf.com/forums/48364/ShowPost.aspx
I wonder if one day, gcc will be able to use -Ostupidity to simplify such
thingies ;)
For those who did not noticed yet, I am just trying to take the piss here.
Thanks ;)
--
Vercetti
On Tuesday 04 October 2005 15:39, Peter Lupton NCH Swift Sound wrote:
> Richard: based on your argument all type checking is for nought :).
>
> But I have been going through other reports from the 'bug book' which I ask
> my programmers to log. Another case which explicit bools would solve would
>
On Sunday 02 October 2005 19:27, Kean Johnston wrote:
> Daniel Berlin wrote:
> > So, now that the new machine is working, i'm starting to get a lot of
> > questions about moving to subversion.
>
> If you're going to move to svn (which idea doesn't thrill me)
> then I hope that the repo will be an F
Hi list
I was told that gcc by default, for every class creates operator =, and
probably something else. This makes binary file bit larger than it suppose to
be. Is it true, and if so, why this is the case ? Can gcc simply not generate
that operator?
--
Vercetti
On Monday 19 September 2005 01:10, Joe Buck wrote:
> On Sun, Sep 18, 2005 at 06:54:26PM +0200, Florian Weimer wrote:
> Generally speaking, we want -Wall to be safe to use. gcc has some
> warnings that can't be silenced without making correct programs
> worse (-Weffc++ comes to mind); these are not
On Saturday 17 September 2005 17:45, you wrote:
> That's a real misunderstanding. There are many warnings that are very
> specialized, and if -Wall really turned on all warnings, it would be
> essentially useless. The idea behind -Wall is that it represents a
> comprehensive set of warnings that mo
On Saturday 17 September 2005 17:18, Gabriel Dos Reis wrote:
> I would also encourage you to conduct a survey of bug frequency in
> codes of people who write programs using functions by *guessing* their
> meanings instead of reading the docs.
>
> I suspect you have much bigger issue to fix than com
On Saturday 17 September 2005 16:23, Gabriel Dos Reis wrote:
> then all you users you know don't read the doc. That is rather
> disappointing, but not uncommon.
It's not that everyone reads manual, you should know. I personally only read
it, when I am missing some piece of information. Do a surve
On Saturday 17 September 2005 15:16, Ian Lance Taylor wrote:
>
> The warning is controlled by -Wsign-compare, which is turned on by
> -Wextra (also known as -W) but not by -Wall. It's not turned on by
> -Wall because it is not normally a problem.
That's strange, all users I know expected it t
On Friday 16 September 2005 19:08, Joe Buck wrote:
> On Sat, Sep 17, 2005 at 01:01:03AM +0800, Tian Dale-A19565 wrote:
> > I encountered a tough situation:
>
> Please, never send messages to both gcc and gcc-help. gcc-help would
>
> have been the right list, except for:
> > (arm_v6_vfp_le-gcc (GCC
On Sunday 14 August 2005 01:39, Tommy Vercetti wrote:
> /home/gj/Projects/gcc/build/gcc/xgcc -B/home/gj/Projects/gcc/build/gcc/
> -B/usr/local/gcc4.0/i686-pc-linux-gnu/bin/
> -B/usr/local/gcc4.0/i686-pc-linux-gnu/lib/
> -isystem /usr/local/gcc4.0/i686-pc-linux-gnu/include
> -isy
/home/gj/Projects/gcc/build/gcc/xgcc -B/home/gj/Projects/gcc/build/gcc/
-B/usr/local/gcc4.0/i686-pc-linux-gnu/bin/
-B/usr/local/gcc4.0/i686-pc-linux-gnu/lib/
-isystem /usr/local/gcc4.0/i686-pc-linux-gnu/include
-isystem /usr/local/gcc4.0/i686-pc-linux-gnu/sys-include -O2 -DIN_GCC-W
-Wall -
On Monday 20 June 2005 10:12, Kai Henningsen wrote:
> [EMAIL PROTECTED] (Tommy Vercetti) wrote on 19.06.05 in
<[EMAIL PROTECTED]>:
> > I was looking on different ones, for C, that claimed to have ability to
> > find security problems. One that I found the best, is splint. B
On Sunday 19 June 2005 04:48, Gabriel Dos Reis wrote:
> Mathieu Malaterre <[EMAIL PROTECTED]> writes:
> | Gabriel Dos Reis wrote:
> | > Tommy Vercetti <[EMAIL PROTECTED]> writes:
> | > | On Sunday 19 June 2005 03:03, you wrote:
> | > | > Elsa does not par
On Sunday 19 June 2005 03:03, you wrote:
> Tommy Vercetti <[EMAIL PROTECTED]> writes:
> | On Sunday 19 June 2005 00:32, you wrote:
> | > Something like:
> | >
> | > http://www.cs.rpi.edu/~gregod/STLlint/STLlint.html
> |
> | Yeah, but for more than just STL, and
rs around,
like elsa, or gcc c++ parser.
> HTH
> Mathieu
>
> Tommy Vercetti wrote:
> > Hi folks
> >
> > I would like to ask you about source validation software. Software that
> > runs trough source code, and attempts to find any possible memory leaks,
> &g
Hi folks
I would like to ask you about source validation software. Software that runs
trough source code, and attempts to find any possible memory leaks, and other
problems. Is there anything opensource for C or/and C++ out there ?
I know it's the wrong list to ask for it, but that's quite clos
Stefan Strasser wrote:
are there any allocation schemes besides garbage collection in gcc
which preserve some memory for reuse which could cause memory leaks if
not cleaned up, or are these bugs? (which don#t matter in the normal
compilation process of course)
I'm using gcc as a library and exp
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19922
--
Vercetti
On Saturday 12 February 2005 14:13, you wrote:
> On Saturday 12 February 2005 13:23, Tommy Vercetti wrote:
> > Hi
> >
> > I've found small issue in ra probably. Maybe there's bug filled out for
> > it already, but I can't find it.
>
> With what y
Hi
I've found small issue in ra probably. Maybe there's bug filled out for it
already, but I can't find it.
For simple loop like that:
for( unsigned int i=0;ihttp://viewcvs.pointblue.com.pl/index.cgi/*checkout*/gj/neurony/neuron.cpp
lines 43-45.
Thanks.
--
Vercetti
23 matches
Mail list logo
