Use of 'simple_name/instance/path attributes - are they any use?

I cant think of any use for these attributes except in assertions, and
even then there is no way of calling something like this:


assert (generics_are_good)
report this'path_name & ": Generics are bad"
severity failure;

So you could identify where the assert output came from. Is there any
way of getting hold of the path of the entity/architecture you are
currently in?

Tricky

On 9 June, 16:49, Tricky <Trickyh...@gmail.com> wrote:
> I cant think of any use for these attributes except in assertions, and
> even then there is no way of calling something *like this:
>
> assert (generics_are_good)
> * report this'path_name & ": Generics are bad"
> * * severity failure;
>
> So you could identify where the assert output came from. Is there any
> way of getting hold of the path of the entity/architecture you are
> currently in?

I mean 'instance_name, not path_name, but it still has the same
problem.

Tricky

Tricky wrote:
> On 9 June, 16:49, Tricky <Trickyh...@gmail.com> wrote:
>> I cant think of any use for these attributes except in assertions,

Me neither. The scope is very limited.
Not much use for a testbench message.
I print custom messages for errors and warnings.

-- Mike Treseler

Mike Treseler

"Tricky" <> wrote in message
news:a6b9c473-4fda-439a-bc7b-...
On 9 June, 16:49, Tricky <Trickyh...@gmail.com> wrote:
> I cant think of any use for these attributes except in assertions, and
> even then there is no way of calling something like this:
>

I've used 'path_name to create the name of a unique log file when the entity
is something that gets reused in a design and where the sim model writes
data to some output file for logging/debugging purposes.

KJ

KJ

Tricky <> writes:

> On 9 June, 16:49, Tricky <Trickyh...@gmail.com> wrote:
>> I cant think of any use for these attributes except in assertions, and
>> even then there is no way of calling something *like this:
>>
>> assert (generics_are_good)
>> * report this'path_name & ": Generics are bad"
>> * * severity failure;
>>
>> So you could identify where the assert output came from. Is there any
>> way of getting hold of the path of the entity/architecture you are
>> currently in?
>
> I mean 'instance_name, not path_name, but it still has the same
> problem.

So long as "this" refers to something like an entity, you can do it.
I've used it for logging msgs in the past.

Unfortunately, when applied to a procedure, it just reports the
procedure name, not back to the entity that called it

Cheers,
Martin
--

TRW Conekt - Consultancy in Engineering, Knowledge and Technology
http://www.conekt.net/electronics.html

Martin Thompson