Re: Help with access types

["James Kerr" <jkerr@southwest.com.au>]

I solved the problem myself, thanks for the comments though

cheers
James
Ken Garlington <Ken.Garlington@computer.org> wrote in message
news:1gqM4.595$X55.75857@news.flash.net...
> Well, other than that they're in the private part of the specification,
> which limits (intentionally)
> which parts of the program can access these variables.
>
> Does the statement "program that is using this specification" mean
something
> other than the body of the
> package (or a private child of this package)?
>
> "Robert Dewar" <robert_dewar@my-deja.com> wrote in message
> news:8dsbq7$26i$1@nnrp1.deja.com...
> > In article <956388888.780287@karri.southwest.com.au>,
> >   "James Kerr" <jkerr@southwest.com.au> wrote:
> > > Okay basically I have a Specification that has this in the
> > private section
> > >
> > > private
> > >
> > >     type Node(Length: Integer);
> > >     type Tree is access node;
> > >     type Tree_Array is array (Integer range <>) of Tree;
> > >     type Node(Length: Integer) is
> > >         record
> > >             Marker: Boolean;
> > >             Symbols: Symbol_Array(1..Length);
> > >             Subtrees: Tree_Array(1..Length);
> > >         end record;
> > >
> > > Okay what is the easiest way to access these record variables,
> > (IE Marker,
> > > Symbols, Length) from a program that is using this
> > specification.
> >
> > Can you give a bit more of an idea of why there is an issue
> > here? There seems to be nothing special about these types that
> > would preclude using normal record and array component notation.
> >
> >
> > Sent via Deja.com http://www.deja.com/
> > Before you buy.
>
>