Mark Lowe wrote:
OT.. Can you give me a straight answer on the issue of localized
required messages just plainly not working?
Sorry, I don't have the time today to follow your i18n thread :-(
--
Reinhard Pötz Independant Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Sourc
Hi Reinhard
What leaps and bounds eh, switch statement support. I'll see if
swapping rhino out works with no shadiness.
OT.. Can you give me a straight answer on the issue of localized
required messages just plainly not working?
Mark
On Thu, 17 Feb 2005 18:01:58 +0100, Reinhard Poetz <[EMAIL P
Mark Lowe wrote:
I imagine that everyone's been too busy developing apps at the speed
of light, on the rapid application development framework known as
cocoon, to have noticed that switch statements don't work with
flowscript, at least when testing strings.
var foo = "bar";
switch(foo) {
case "ba
Least it wasn't that I'd forgotten how to write a trusty switch
statement then :o)
I've used a dirty
foo = "bar"?print("Mellow world"):null;
Mark
On Thu, 17 Feb 2005 13:26:55 +0100, Jan Hinzmann <[EMAIL PROTECTED]> wrote:
> i realised that too, and therefore am using if-else combinations now.
>
i realised that too, and therefore am using if-else combinations now.
I think having the switch-statement working with strings depends on the
javascript-distribution.
In java itself, you cannot "switch over strings", but you can define constants
and switch over them.
var MY_CONSTANT1 = 1;
var
I imagine that everyone's been too busy developing apps at the speed
of light, on the rapid application development framework known as
cocoon, to have noticed that switch statements don't work with
flowscript, at least when testing strings.
var foo = "bar";
switch(foo) {
case "bar" : print("swi
