Mail Archives: djgpp/1995/11/29/15:26:13

Xref: comp.lang.c++:59071 comp.os.msdos.djgpp:3480
From: "Michael E. Wesolowski" <mewesolo AT freenet DOT calgary DOT ab DOT ca>
Newsgroups: comp.os.msdos.djgpp,comp.lang.c++
Subject: Declaring arrays inside generic function
Date: Mon, 27 Nov 1995 20:37:32 -0700
Organization: Calgary Free-Net
Lines: 25
Nntp-Posting-Host: mewesolo AT srv1 DOT freenet DOT calgary DOT ab DOT ca
To: djgpp AT sun DOT soe DOT clarkson DOT edu
Dj-Gateway: from newsgroup comp.os.msdos.djgpp

I don't know if this is a problem with gcc, the DOS port of gcc, or 
something (i.e., not a bug) in the implementation that I don't know 
about. I'm using the DOS port of gcc (djgpp), v1.12m4. This is equivalent 
ot gcc 2.6.3, if I remember correctly.

I have a generic function which has as one of its input parameters an int 
which identifies an array size. Within the function, I attempt to declare 
an array of int's:

int item_count [array_size];

where array_size is the input parameter. When I look at the array in the 
debugger (gdb) however, what i see is an array of int pointers (I think) 
- something like int (*) [60000] (the 60000 is approximate). If I 
explicitly declare the array as, for example, item_count [10], I get the 
expected array of 10, uninitialized ints. SO, what's the problem?

If it's something in the ANSI standard, I'd appreciate the paragraph 
reference as well as a simple description of what's going on. Thanks.


Michael Wesolowski (mewesolo AT freenet DOT calgary DOT ab DOT ca)

- Raw text -

  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019