If TProcess.CommandLine is deprecated...

...what should i use instead?
________________________________
William de Oliveira Ferreira
Bacharel em Sistemas de Informa??o
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20120206/d847f0b8/attachment.html>

You can use

*.Parameters.Text:='Parm1 Param2'
*.Parameters.DelimitedText:='Parm1=1 Param2=2'

2012/2/6 William Oliveira Ferreira :

Andrew Brunner wrote

You can use *.Parameters.Text:='Parm1 Param2' *.Parameters.DelimitedText:='Parm1=1 Param2=2'

Or better yet
Parameters.Add('Parm1');
Parameters.Add('Parm2');

and of course, use Executable to indicate the binary.

All this is documented and explained in:

http://www.freepascal.org/docs-html/fcl/process/tprocess.commandline.html

Michael.

thanks!
________________________________
William de Oliveira Ferreira
Bacharel em Sistemas de Informa??o

2012/2/7

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20120207/3ce4592d/attachment-0001.html>

2012/2/7 :

All this is documented and explained in: http://www.freepascal.org/docs-html/fcl/process/tprocess.commandline.html

Oh, this must be new. It seems I need a fresh set of .chm files. (Just this weekend I stumbled over the same question and did not find it in the help and also no helpful comments inside the TProcess source code.

(btw: the source code was the first place I intuitively hoped to find an answer, a short comment behind the "deprecated" keyword, but there is nothing)

I agree that a comment in front of the deprecated would be good to the uninformed as me, but I also do not want to seem boring. I wish developers would focus on tools for debugging, but follow the road map and I see good things to come.

//translated with help of google translator
________________________________
William de Oliveira Ferreira
Bacharel em Sistemas de Informa??o

2012/2/7 Bernd

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20120208/2638b96e/attachment-0001.html>

William Oliveira Ferreira wrote

I agree that a comment in front of the deprecated would be good to the uninformed as me, but I also do not want to seem boring. I wish developers would focus on tools for debugging, but follow the road map and I see good things to come.

A comment in front of the deprecated won't be good, but a string behind the deprecated would be nice ;) (for the reason see below)

=== example begin ===

program deprecatedtest;
type
   TTest = class
     fFoo: String;
     property Foo: String read fFoo; deprecated 'I''m not needed anymore';
   end;
var
   t: TTest;
begin
   t := TTest.Create;
   Writeln(t.Foo);
end.

=== example end ===

=== output begin ===

PS P:\tests\oneshots> fpc .\deprecatedtest.pas
Free Pascal Compiler version 2.6.0 [2011/12/25] for i386 Copyright (c) 1993-2011 by Florian Klaempfl and others Target OS: Win32 for i386
Compiling .\deprecatedtest.pas
deprecatedtest.pas(15,13) Warning: Symbol "Foo" is deprecated: "I'm not needed anymore"
Linking deprecatedtest.exe
16 lines compiled, 0.1 sec , 28608 bytes code, 1964 bytes data 1 warning(s) issued

=== output end ===

Regards,
Sven

How about in the SetCommandLine, of the property CommandLine he does the split between exename and parameters. By this, the two options could be available. Of course, who puts a parameter with space and not set the " " will deal with some error, which is good to learn. About that, could be created some manner to offer hints and tips on code editor in how about to use de elements of the class. It's will be very good documentation and also very good IDE behavior.

you told correclty what i was trying to say wrongly.... =) ________________________________
William de Oliveira Ferreira
Bacharel em Sistemas de Informa??o

2012/2/8 Sven Barth

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20120208/1a7f75cc/attachment.html>

The concept of deprecated is that is not needed anymore so tell that doesn't help much.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20120208/10d7b67a/attachment-0001.html>

well, so i'll gonna be mor clear:
just say that a property or function is deprecated without take a hint of what should be better used is obscure. just a hint of what should be used i'll help a lot..
________________________________
William de Oliveira Ferreira
Bacharel em Sistemas de Informa??o

2012/2/8 Everton Vieira

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20120208/ba1f9b67/attachment.html>

That's true, if the procedure is really deprecated, then the question is what use instead.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20120208/c4ff6c16/attachment.html>

Everton Vieira wrote

That's true, if the procedure is really deprecated, then the question is what use instead.

In case of TProcess.CommandLine it's mentioned here: http://www.freepascal.org/docs-html/fcl/process/tprocess.commandline.html (though it could have been mentioned in the deprecated message as well...)

Regards,
Sven

Yeah, the documentation of it, are very good.

Please, answer a silly question of mine, the deprecated functions are dropped?

Everton Vieira wrote

Yeah, the documentation of it, are very good. Please, answer a silly question of mine, the deprecated functions are dropped?

That should be the long term goal. As the deprecated for that property was introduced for 2.6.0 it might be that they'll be removed in 2.8.0... (not in 2.6.2 or 2.6.4 for sure though).

Regards,
Sven

Make sense. Thanks.

But the previous idea of show the net development of the documentation with examples and tips of use it in the IDE is very good. The help of the delphi was always good, i remember the early days that i`ve successfully used.

And the idea of keep multiple functionalities with different behaviors is also good, the problem in that is the rain of question that could came, and the solution of it is an good IDE help. And as an open source project the net development of the documentation should be include in the that help.

well, so i'll gonna be mor clear: just say that a property or function is deprecated without take a hint of what should be better used is obscure. just a hint of what should be used i'll help a lot..

I wonder why such *obvious* things deserve any discussion ;-)

DoDi

well, i think it shoundn't but when we find these mistakes, it normal that someone starts to question...
________________________________
William de Oliveira Ferreira
Bacharel em Sistemas de Informa??o

2012/2/8 Hans-Peter Diettrich

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20120208/dc817155/attachment.html>

2.6.0 must be compilable with 2.4.4.

So the fact that 2.6.0 compiles messages to "deprecated" (*) only has an effect on 2.6.2 and beyond.

(*) and in reality, the docs tool must survive it also.

Right... I forgot about that (though one could have added a compiler condition around the message - which does not mean that you should have done that!)

(*) and in reality, the docs tool must survive it also.

That is indeed also important :)

Regards,
Sven