35 replies to this topic

[Lancelot]

Thanks for the warning psc

I was trying to use Quote all the time as an old habit, Reason comment by Medevil "So that everyone and their dog started adding "" whereever possible" . (ps: i have no spaced path too )

what i learn from the topic is:
try to use quote only with path related things , try to avoid using quotes in other places whenever possible .

But
I hope on future versions of wb using
Set,"%value1%","1234,5 6,7 8"
remains the same as before, because it is much easier to understand/read than
Set,"%value2%",1234#$c5#$s6#$c7#$s8



I agree with Medevil "fault tolerance is not a good idea" for many cases, not having will help much for projects to be more backward compatible. Maybe For a while it will be better with showing "fault tolerance"'s as warnings during 077betas .

With experience by LiveXP and reasons written longly before on wb077b1 topic, contrary with Peter psc and maybe Nuno, i believe it is better for a project to follow wb versions even they are nightly build or beta, otherwise you get a looooooong list of warnings and errors by jumping from one stable to other stable. Yes, it is very bad not to have backward compatibility (ps: currently LiveXP bootsdi dont work with wb077b1), i hope the price we pay these days will lead better backward compatibility for future releases.



Topic is about "Qutoe, Comma, Space" but i have a question for "percentage"
is there any rule/comment for using variable in variable (i had some issues that i can not remember now, following lines works):

Set,%test%,peter

Set,%petervariable%,peter#$sin#$sbootland

Echo,%%test%variable%

[pscEx]

I hope on future versions of wb using
Set,"%value1%","1234,5 6,7 8"
remains the same as before, because it is much easier to understand/read than
Set,"%value2%",1234#$c5#$s6#$c7#$s8

In general that should work as before.
But it may happen in certain situations (I do not know one yet) that it will not work. Then unfortunattelly the script developer has to use the 'correct' method.

Topic is about "Qutoe, Comma, Space" but i have a question for "percentage"
is there any rule/comment for using variable in variable (i had some issues that i can not remember now, following lines works):

Set,%test%,peter

 Set,%petervariable%,peter#$sin#$sbootland

 Echo,%%test%variable%

There are no special rules. Variables inside a variable (I call them 'nested variables') should work in all cases.
Nested variables are thought to run in the way you show. They are tested and got the 'certification'.
%test% is replaced by peter > %%test%variable% >> %petervariable%
And therefore the echo is :peter#$sin#$sbootland > peter in bootland

However, as usual in a product under development, maybe there are constellations where this dos not work. That would be a reason to visit the bug tracker.

Peter

[Brito]

Set,"%List%","a,b,c"

Run,"%ScriptFile%",Test,%list%

  

[Test]

Echo,"#1"

Echo,"#2"

Echo,"#3"

Allan, I don't think Peter is doing this on purpose but rather trying to fix a reported bug.

wb's script engine has a worldwide-known reputation for allowing all sort of possible codings but sometimes it's certainly not easy to predict every possible situation when trying to improve the current state of things.

So, should the prevous behavior be adopted as default for the run command?

[allanf]

Set,"%List%","a,b,c"

Run,"%ScriptFile%",Test,%list%

  

[Test]

Echo,"#1"

Echo,"#2"

Echo,"#3"

Allan, I don't think Peter is doing this on purpose but rather trying to fix a reported bug.

wb's script engine has a worldwide-known reputation for allowing all sort of possible codings but sometimes it's certainly not easy to predict every possible situation when trying to improve the current state of things.

So, should the prevous behavior be adopted as default for the run command?

@Nuno,

Where is the reported bug?

comma is used as a separator throughout winbuilder script.

If someone wishes the commas as string rather than separator...

Thanks anyway... I cannot continue.

Bye

[Lancelot]

For this case, i support new wb077b1 method

reason is, if i set a variable with comma and in quotes and use #1 i expect it totally as written
i mean with writing
Set,"%List%","a,b,c"
i expect
Echo,"#1"
resulting with
a,b,c

i wont expect only
a
because a,b,c are in quotes


This is the logic so far i know in wb batching, I guess this was a bugy (reported or not) and fixed by peter psc. But sadly bugy behaviour used (i guess a lot) by allanf.
if continued with bugy like allanf suggest, how can a user get #1=a #2=b,c
this doesnt work with 076/77b1 (tested some other combinations too with #$ )

Set,"%List%","a,"b,c""

Echo,"#1"

Echo,"#2"

I believe allanf demanding is very logic but with a more expected wb batching method it will be a nice improvement for wb to have

[process]

Set,"%List%",a,b,c



[Test]

Echo,"#1"

Echo,"#2"

Echo,"#3"

with other words

[process]

Set,"%List%","a","b","c"



[Test]

Echo,"#1"

Echo,"#2"

Echo,"#3"

which results with allanf expectance.
a
b
c

Set,"%List%","a","b,c"

Echo,"#1"

Echo,"#2"

or this one resulting with
a
b,c



Hoping available in shortwhile future version if allanf, peter and other like the idea ( 077b2 )

I believe this improvement will help allanf fix through his scripts quickly


I hope it is that much easy to fix other bugy things in scripts with new versions of wb (wimpack lookin to me, i am looking to her with deep eye contact for a looong while, we will love or hate in the end but bootsdi blinking at the back and a regfactory soccer team waiting for a match )

[pscEx]

Seems like a sensible change to me. However as it does introduce compatibility problems maybe you should make it optional at the script level i.e. require a new option in the [main] section of a script to enable the new syntax.

Would not like winbuilder to be like MS products which never seem to care about compatibility with earlier versions of the product.

Next beta this is possible:

[process]

Set,%List%,"a,b,c"

Run,%ScriptFile%,Test,%List%

System,SPLITPARAMETERS,ON

Run,%ScriptFile%,Test,%List%

System,SPLITPARAMETERS,OFF



[Test]

Echo,#1

Echo,#2

Echo,#3

With result:
Processing section: [process]
File [%BaseDir%\Projects\win7_pe\CodeBox.txt] Version [1]

SetVar - Sucessfuly changed the value of [%List%] to: [a#$cb#$cc]
Run - Processing section: [Test] From file: [%BaseDir%\Projects\win7_pe\CodeBox.txt]
with parameters: [a,b,c]
a,b,c


Run - Processed section [Test] in file: [%BaseDir%\Projects\win7_pe\CodeBox.txt]
System,SplitParameters,ON
Run - Processing section: [Test] From file: [%BaseDir%\Projects\win7_pe\CodeBox.txt]
with parameters: [a],[b],[c]
a
b
c
Run - Processed section [Test] in file: [%BaseDir%\Projects\win7_pe\CodeBox.txt]
System,SplitParameters,OFF

The System,SPLITPARAMETERS,ON command can be given once in the project, e.g. in [Process] of script.project, and is then valid for the complete project (or until it is switched off by System,SPLITPARAMETERS,OFF, and then switched on again, and ....)

Peter

BTW: This again is one of the commands, I only invented for MY nativeEx project.
In spite it is currently not needed there, I'm going to find sth where to use it.
Suggestions welcome!

[Lancelot]

Peter

with new b2, does this result

[process]

Set,%List%,"a,b","c"

System,SPLITPARAMETERS,ON

Run,%ScriptFile%,Test,%List%

System,SPLITPARAMETERS,OFF



[Test]

Echo,"#1"

Echo,"#2"

with:

a,b
c



or by using #1 #2 what is the correct way to get ?
a,b
c

[pscEx]

Add it as argument to the 'Run'

The Set command can assign ONLY ONE value, not two like you try!

Peter

[Lancelot]

yep i am aware


than

[process]

Set,%List%,"a#$cb,c"

System,SPLITPARAMETERS,ON

Run,%ScriptFile%,Test,%List%

System,SPLITPARAMETERS,OFF



[Test]

Echo,"#1"

Echo,"#2"

may result with

a,b
c

??

ps: i just try to show future problem/issue with comma , I feel with new System,SPLITPARAMETERS features the example on this post should work with wb077b2

[pscEx]

The SPLITPARAMETER is only made to hold compatibility for those scripts, who used a "bug's feature" for their functionality.

For all others is:

ONE parameter is ONE parameter, regardles whether it contains spaces, commas etc. or not.

Peter

[Lancelot]

Dont get angry Peter

okey , bugy feature is now a real feature and there is no new feature around. I just shared my thoughts for future , that is all