If you want to pass _any_ pointer (variant) to a block (with non-optimized access), you need to know what a 0 pointer looks like (so you can test your code).

In the event a block needs to be called, and the variant in/out tag is not needed, you can pass a zero pointer - rather than making the tag optional which can be tricky. 

[ATamas]

Dear Experts,

I have experimented with variant and read some docs which lead me to this page.

On that page there is a table where the last row contains this:

P#Zero value1)

P#0.0 VOID 0, ZERO1)

I thought this could be a /dev/zero like thing that unix like systems have been using for long years.

However I wont be able to get it work neither on an S71200 nor an S71500 CPU.

Does anyone have an idea how it should be used?

Thank you in advance,

aTom

[ATamas]

Dear Experts,

I have experimented with variant and read some docs which lead me to this page.

On that page there is a table where the last row contains this:

P#Zero value1)

P#0.0 VOID 0, ZERO1)

I thought this could be a /dev/zero like thing that unix like systems have been using for long years.

However I wont be able to get it work neither on an S71200 nor an S71500 CPU.

Does anyone have an idea how it should be used?

Thank you in advance,

aTom

A screen grab of how the implementation looks like, would be most welcome.
A description of your use case would be nice too.

[ATamas]

I have experimented with variant and read some docs which lead me to this page.

On that page there is a table where the last row contains this:

P#Zero value1)

P#0.0 VOID 0, ZERO1)

I thought this could be a /dev/zero like thing that unix like systems have been using for long years.

If you expect something behaving like unix-like /dev/zero then no luck. Nothing like this exists on the system.

Variant is some kind of reference. What is described in the mentioned manual is a null reference (actually it is a null pointer). You can / should use the NULL constant. Or while checking - IS_NULL(variant)/NOT_NULL(variant).