Re: [WebDNA] for a rainy day.. if ever/when the hood is up again on the [function]/[return] code

This WebDNA talk-list message is from

2011

It keeps the original formatting. numero = 107502
interpreted = N
texte = >> Feature request:>>=20>> correct me if I am wrong, but it would be more modern if parsing =would drop out of the [function] (with the [return] val.) whenever =[return] was hit. I.e. it should be allowed to have many [return]'s =inside conditionals.. inside the function... so we can just up and =decide to jump out of the function with the return val at that point.>=20>=20> The functionality of not breaking out of the function context when =hitting a [return][/return] was by design.. this was so people can =sculpt returns... ie., string of variables...>=20> -----------------------> [function ..]> [return]f_string=3D[/return]> [showif blah=3D]> [return]&f_something=3D[/return]> [/showif]> [showif otherblah=3D]> [return]&f_other=3D[/return]> [/showif]> [/function]> ---->=20> [f_string]> [f_something]> [f_other]> ---------------------->=20> sure, the above could be done other ways.. but the functionality adds =some useful properties in my opinion.>=20> DonovanHi Donovan,=20Thanks for pointing that out. So now I see it is a (useful) feature, =and not just weird. I will have to approach Webdna [return] differently =than I have been to make use of it like that. Anyway good to know. =20Funny how in Webdna [return] does not break out, but a case (in switch) =will, ...while in PHP return breaks out, while a case (in switch) will =not (without explicit "break"). =20-G Associated Messages, from the most recent to the oldest:

Re: [WebDNA] for a rainy day.. if ever/when the hood is up again on the [function]/[return] code (Govinda 2011)
Re: [WebDNA] for a rainy day.. if ever/when the hood is up again on the [function]/[return] code (Govinda 2011)
[WebDNA] for a rainy day.. if ever/when the hood is up again on the [function]/[return] code (Govinda 2011)

>> Feature request:>>=20>> correct me if I am wrong, but it would be more modern if parsing =would drop out of the [function] (with the [return] val.) whenever =[return] was hit. I.e. it should be allowed to have many [return]'s =inside conditionals.. inside the function... so we can just up and =decide to jump out of the function with the return val at that point.>=20>=20> The functionality of not breaking out of the function context when =hitting a [return][/return] was by design.. this was so people can =sculpt returns... ie., string of variables...>=20> -----------------------> [function ..]> [return]f_string=3D[/return]> [showif blah=3D]> [return]&f_something=3D[/return]> [/showif]> [showif otherblah=3D]> [return]&f_other=3D[/return]> [/showif]> [/function]> ---->=20> [f_string]> [f_something]> [f_other]> ---------------------->=20> sure, the above could be done other ways.. but the functionality adds =some useful properties in my opinion.>=20> DonovanHi Donovan,=20Thanks for pointing that out. So now I see it is a (useful) feature, =and not just weird. I will have to approach Webdna [return] differently =than I have been to make use of it like that. Anyway good to know. =20Funny how in Webdna [return] does not break out, but a case (in switch) =will, ...while in PHP return breaks out, while a case (in switch) will =not (without explicit "break"). =20-G Govinda

DOWNLOAD WEBDNA NOW!

Re: [WebDNA] for a rainy day.. if ever/when the hood is up again on the [function]/[return] code

2011

Top Articles:

Related Readings: