Re: Returning an array from a function.

From: Steve (aeroman10_at_nospam-yahoo.com)
Date: 09/03/04 

Date: Fri, 03 Sep 2004 20:35:36 GMT

> Have you looked at std::vector<> yet? They are much easier (and safer) to
> use than arrays.

If I were doing this for myself I would probably look into that but
unfortunately I am required to use arrays.

Also I said that I cannot use pointers, turns out its wrong, I am able to
use both references and/or pointers to accomplish this.

Still trying to figure this out.

Relevant Pages

  • Re: Fat references
    ... traditional style of placing a header with GC metadata before every value ... So now you have references that can't fit into a machine register. ... Fat pointers have been implemented in some C compilers, ... run-time bounds checking on arrays and other objects. ...
    (comp.compilers)
  • Re: Fat references
    ... traditional style of placing a header with GC metadata before every value ... So now you have references that can't fit into a machine register. ... Fat pointers have been implemented in some C compilers, ... run-time bounds checking on arrays and other objects. ...
    (comp.compilers)
  • Re: Array comparison
    ... > Deep and recursive. ... the pointers and comparing their referents instead of comparing the ... >> arrays, then I think you also need to argue against assigning arrays. ... semantics (notably, reference counting). ...
    (alt.comp.lang.borland-delphi)
  • Re: Fat references
    ... pointers to unconstrained arrays. ... fat pointers are the solution. ... extra code to convert the C array into a fat reference in that stub, ...
    (comp.compilers)
  • Re: double pointer
    ... Nor is it up to me, Deitel 1, Deitel 2, Schildt, ... that arrays are pointers, or that pointers are arrays, in C++. ...
    (comp.lang.c)