aprocess.environment

[toby]

dude you are being dishonest here

the discussion has alway been about the child process and not about the parent process that is what aprocess.environment does lol

where are you apolgy for you code comment and for the

for i := -100 to (getenvironmentvariablecount - 1) do writeln('getenvironmentstring(', i, ') : ', getenvironmentstring(i));

simplistic use of env?   lol   you are to dishonest to deal with     i was the one saying what you are now saying  and you said it wasn't true

[lucamar]

You get one apology (and a correction) because DOS.EnvStr() effectively starts form one, despite what the documentation says.

For some reason my previous test was giving correct results even for EnvStr(0). In a new even simpler one it just returns an empty string (as do anything other than [1..EnvCount]).

As for this:

the discussion has alway been about the child process and not about the parent process that is what aprocess.environment does lol

That has been exactly my contention all along! It's now clear that we have been talking at cross-purposes. If you had started by saying: "I am running env with a TProcess to check what the passed environment looks like and ..." we would not have wasted so many electrons.

So let's just leave it here, forget the hot words caused by temper and close the discussion, shall we?

[toby]

okay you have been very very helpful - so thanks  even the 'misunderstanding' has been greatly helpful in exploring things and understanding what is capable with the fpc coding


but the only way you can use env is in a tprocess

[dsiders]

okay you have been very very helpful - so thanks  even the 'misunderstanding' has been greatly helpful in exploring things and understanding what is capable with the fpc coding


but the only way you can use env is in a tprocess

Try decaf.

[lucamar]

but the only way you can use env is in a tprocess

Or on a terminal.

[toby]

yea but won't help much in working with aprocess.environment

[PascalDragon]

You get one apology (and a correction) because DOS.EnvStr() effectively starts form one, despite what the documentation says.

That should probably be reported then... (especially as the example in the documentation starts at 1 )