Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.javascript > #36868 > unrolled thread

Rudimentary programming methodology

Back to article view | Back to comp.lang.javascript

Contents

  Rudimentary programming methodology Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-06-12 14:40 -0700
    Re: Rudimentary programming methodology "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2019-06-12 23:54 +0200
      Re: Rudimentary programming methodology Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-06-12 23:41 -0700
        Re: Rudimentary programming methodology Arno Welzel <usenet@arnowelzel.de> - 2019-06-13 11:27 +0200
      Re: Rudimentary programming methodology Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-06-12 23:56 -0700
        Re: Rudimentary programming methodology Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-06-13 00:49 -0700
          Re: Rudimentary programming methodology Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-06-13 00:57 -0700
            Re: Rudimentary programming methodology Arno Welzel <usenet@arnowelzel.de> - 2019-06-13 11:31 +0200
              Re: Rudimentary programming methodology Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-06-13 03:19 -0700
              Re: Rudimentary programming methodology Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-06-13 03:21 -0700
              Re: Rudimentary programming methodology Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-06-13 03:26 -0700
                Re: Rudimentary programming methodology Arno Welzel <usenet@arnowelzel.de> - 2019-06-13 13:43 +0200
          Re: Rudimentary programming methodology Arno Welzel <usenet@arnowelzel.de> - 2019-06-13 11:29 +0200
            Re: Rudimentary programming methodology Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-06-13 03:13 -0700
              Re: Rudimentary programming methodology "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2019-06-13 12:24 +0200
                Re: Rudimentary programming methodology Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-06-13 03:36 -0700
                  Re: Rudimentary programming methodology Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-06-13 03:48 -0700
                    Re: Rudimentary programming methodology Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-06-13 03:56 -0700
                    Re: Rudimentary programming methodology Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-06-13 04:01 -0700
                      Re: Rudimentary programming methodology Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-06-13 04:03 -0700
                      Re: Rudimentary programming methodology Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-06-13 04:10 -0700
                        Re: Rudimentary programming methodology Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-06-13 04:14 -0700
                          Re: Rudimentary programming methodology Arno Welzel <usenet@arnowelzel.de> - 2019-06-13 13:45 +0200
                        Re: Rudimentary programming methodology Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-06-15 03:36 -0700
                          Re: Rudimentary programming methodology "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2019-06-15 13:49 +0200
                            Re: Rudimentary programming methodology Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-06-15 06:31 -0700
                          Re: Rudimentary programming methodology dr.j.r.stockton@gmail.com - 2019-06-15 07:40 -0700
                            Re: Rudimentary programming methodology Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-06-15 08:25 -0700
    Re: Rudimentary programming methodology JJ <jj4public@vfemail.net> - 2019-06-13 15:13 +0700
    Re: Rudimentary programming methodology dr.j.r.stockton@gmail.com - 2019-06-13 04:20 -0700

Page 1 of 2  [1] 2  Next page →

#36868 — Rudimentary programming methodology

I have a problem that i should know howto solve it is probably very basic.

Normally when you have choices, the most common way is to solve it with if, else if.

But sometimes your choices is fundamental to a process, so they are the input parmeters for something.

In my case i have a metronome, but depending on the "synth/hardware" you want to use you simply select it from an option list.

And now i could do 

if (met=="external") {something sent to port)
else if (met=="othersynth") {something else sent to port}
else if (met=="anothersynth") {something else sent to port}


If these are timed events it is not that effective to do this x times a second.

So you just want check and set the case once? and then be used everytime during the interval?

I guess that means to breakout the if cases into functions?
But you just want the actual function call to differ, but not be checked every time you send something to the metronome.

Basicly about setting what function to be called once, like flipping a switch and then it always take that "path".

I have a slight memory it could be case programming using switches, but i don't quite see hot it applies dealing with timed events during an interval?

Basicly i want to replace if else if before every metronome event.

[toc] | [next] | [standalone]

#36869

=?UTF-8?Q?Jonas_Th=C3=B6rnvall?= <jonas.thornvall@gmail.com> wrote on 12
Jun 2019 in comp.lang.javascript: 

> I have a problem that i should know howto solve it is probably very
> basic. 
> 
> Normally when you have choices, the most common way is to solve it with
> if, else if. 
> 
> But sometimes your choices is fundamental to a process, so they are the
> input parmeters for something. 
> 
> In my case i have a metronome, but depending on the "synth/hardware" you
> want to use you simply select it from an option list. 
> 
> And now i could do 
> 
> if (met=="external") {something sent to port)
> else if (met=="othersynth") {something else sent to port}
> else if (met=="anothersynth") {something else sent to port}
> 
> 
> If these are timed events it is not that effective to do this x times a
> second. 
> 
> So you just want check and set the case once? and then be used everytime
> during the interval? 
> 
> I guess that means to breakout the if cases into functions?
> But you just want the actual function call to differ, but not be checked
> every time you send something to the metronome. 
> 
> Basicly about setting what function to be called once, like flipping a
> switch and then it always take that "path". 
> 
> I have a slight memory it could be case programming using switches, but
> i don't quite see hot it applies dealing with timed events during an
> interval? 
> 
> Basicly i want to replace if else if before every metronome event.

Basically you are not making sense,
even for one professing a slight memory. 

Your timing requirements ar by large not short enough 
to require machine language decision speeds.

Scripting language witches internally are just if-else-then constructs,
and are perfect to implement logic showing a clearer human visible script, 
not for much faster execution.

-- 
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)

[toc] | [prev] | [next] | [standalone]

#36872

Den torsdag 13 juni 2019 kl. 00:45:19 UTC+2 skrev Evertjan.:
> =?UTF-8?Q?Jonas_Th=C3=B6rnvall?= <jonas.thornvall@gmail.com> wrote on 12
> Jun 2019 in comp.lang.javascript: 
> 
> > I have a problem that i should know howto solve it is probably very
> > basic. 
> > 
> > Normally when you have choices, the most common way is to solve it with
> > if, else if. 
> > 
> > But sometimes your choices is fundamental to a process, so they are the
> > input parmeters for something. 
> > 
> > In my case i have a metronome, but depending on the "synth/hardware" you
> > want to use you simply select it from an option list. 
> > 
> > And now i could do 
> > 
> > if (met=="external") {something sent to port)
> > else if (met=="othersynth") {something else sent to port}
> > else if (met=="anothersynth") {something else sent to port}
> > 
> > 
> > If these are timed events it is not that effective to do this x times a
> > second. 
> > 
> > So you just want check and set the case once? and then be used everytime
> > during the interval? 
> > 
> > I guess that means to breakout the if cases into functions?
> > But you just want the actual function call to differ, but not be checked
> > every time you send something to the metronome. 
> > 
> > Basicly about setting what function to be called once, like flipping a
> > switch and then it always take that "path". 
> > 
> > I have a slight memory it could be case programming using switches, but
> > i don't quite see hot it applies dealing with timed events during an
> > interval? 
> > 
> > Basicly i want to replace if else if before every metronome event.
> 
> Basically you are not making sense,
> even for one professing a slight memory. 
> 
> Your timing requirements ar by large not short enough 
> to require machine language decision speeds.
> 
> Scripting language witches internally are just if-else-then constructs,
> and are perfect to implement logic showing a clearer human visible script, 
> not for much faster execution.
> 
> -- 
> Evertjan.
> The Netherlands.
> (Please change the x'es to dots in my emailaddress)

So you say an if else every x milliseconds is ok?
Let say it would 10 choices would it still be ok?

[toc] | [prev] | [next] | [standalone]

#36879

On 13.06.19 08:41, Jonas Thörnvall wrote:

[...]
> So you say an if else every x milliseconds is ok?
> Let say it would 10 choices would it still be ok?

Yes. JavaScript is fast enough nowadays to run even complete games in 3D
in the browser:

<http://www.quakejs.com/>



-- 
Arno Welzel
https://arnowelzel.de

[toc] | [prev] | [next] | [standalone]

#36873

Den torsdag 13 juni 2019 kl. 00:45:19 UTC+2 skrev Evertjan.:
> =?UTF-8?Q?Jonas_Th=C3=B6rnvall?= <jonas.thornvall@gmail.com> wrote on 12
> Jun 2019 in comp.lang.javascript: 
> 
> > I have a problem that i should know howto solve it is probably very
> > basic. 
> > 
> > Normally when you have choices, the most common way is to solve it with
> > if, else if. 
> > 
> > But sometimes your choices is fundamental to a process, so they are the
> > input parmeters for something. 
> > 
> > In my case i have a metronome, but depending on the "synth/hardware" you
> > want to use you simply select it from an option list. 
> > 
> > And now i could do 
> > 
> > if (met=="external") {something sent to port)
> > else if (met=="othersynth") {something else sent to port}
> > else if (met=="anothersynth") {something else sent to port}
> > 
> > 
> > If these are timed events it is not that effective to do this x times a
> > second. 
> > 
> > So you just want check and set the case once? and then be used everytime
> > during the interval? 
> > 
> > I guess that means to breakout the if cases into functions?
> > But you just want the actual function call to differ, but not be checked
> > every time you send something to the metronome. 
> > 
> > Basicly about setting what function to be called once, like flipping a
> > switch and then it always take that "path". 
> > 
> > I have a slight memory it could be case programming using switches, but
> > i don't quite see hot it applies dealing with timed events during an
> > interval? 
> > 
> > Basicly i want to replace if else if before every metronome event.
> 
> Basically you are not making sense,
> even for one professing a slight memory. 
> 
> Your timing requirements ar by large not short enough 
> to require machine language decision speeds.
> 
> Scripting language witches internally are just if-else-then constructs,
> and are perfect to implement logic showing a clearer human visible script, 
> not for much faster execution.
> 
> -- 
> Evertjan.
> The Netherlands.
> (Please change the x'es to dots in my emailaddress)

Even if it is not necessary in my case, is there a construct to handle this type of problems in Javascript? It must be something with realtime switches of sort.

It seem analogue to setting a switch to chose a leg/route "before" the actual timed events take place?

Is there a typecase for howto solve these types of problems?
Because i am a bit stumped for how i should tackle this type of problem?
They seem to create full legs with much more code then the actual choice of metronome? I could solve this type of problem with alot of code duplicated, but there must be some construct to just handle the explicit choice of metronome?

[toc] | [prev] | [next] | [standalone]

#36875

Den torsdag 13 juni 2019 kl. 08:57:06 UTC+2 skrev Jonas Thörnvall:
> Den torsdag 13 juni 2019 kl. 00:45:19 UTC+2 skrev Evertjan.:
> > =?UTF-8?Q?Jonas_Th=C3=B6rnvall?= <jonas.thornvall@gmail.com> wrote on 12
> > Jun 2019 in comp.lang.javascript: 
> > 
> > > I have a problem that i should know howto solve it is probably very
> > > basic. 
> > > 
> > > Normally when you have choices, the most common way is to solve it with
> > > if, else if. 
> > > 
> > > But sometimes your choices is fundamental to a process, so they are the
> > > input parmeters for something. 
> > > 
> > > In my case i have a metronome, but depending on the "synth/hardware" you
> > > want to use you simply select it from an option list. 
> > > 
> > > And now i could do 
> > > 
> > > if (met=="external") {something sent to port)
> > > else if (met=="othersynth") {something else sent to port}
> > > else if (met=="anothersynth") {something else sent to port}
> > > 
> > > 
> > > If these are timed events it is not that effective to do this x times a
> > > second. 
> > > 
> > > So you just want check and set the case once? and then be used everytime
> > > during the interval? 
> > > 
> > > I guess that means to breakout the if cases into functions?
> > > But you just want the actual function call to differ, but not be checked
> > > every time you send something to the metronome. 
> > > 
> > > Basicly about setting what function to be called once, like flipping a
> > > switch and then it always take that "path". 
> > > 
> > > I have a slight memory it could be case programming using switches, but
> > > i don't quite see hot it applies dealing with timed events during an
> > > interval? 
> > > 
> > > Basicly i want to replace if else if before every metronome event.
> > 
> > Basically you are not making sense,
> > even for one professing a slight memory. 
> > 
> > Your timing requirements ar by large not short enough 
> > to require machine language decision speeds.
> > 
> > Scripting language witches internally are just if-else-then constructs,
> > and are perfect to implement logic showing a clearer human visible script, 
> > not for much faster execution.
> > 
> > -- 
> > Evertjan.
> > The Netherlands.
> > (Please change the x'es to dots in my emailaddress)
> 
> Even if it is not necessary in my case, is there a construct to handle this type of problems in Javascript? It must be something with realtime switches of sort.
> 
> It seem analogue to setting a switch to chose a leg/route "before" the actual timed events take place?
> 
> Is there a typecase for howto solve these types of problems?
> Because i am a bit stumped for how i should tackle this type of problem?
> They seem to create full legs with much more code then the actual choice of metronome? I could solve this type of problem with alot of code duplicated, but there must be some construct to just handle the explicit choice of metronome?

I guess this is maybe also about programming language methodology?

What would been awesome in languages would be...."i just dealt with highlevel Turbo Pascal, a little C , Java and javascript

A construct? like this.

Case A {do this}
Case B {do that}
Case C {do something else}

If switch=A {Case:A)} else if switch=B {Case:B)}elseif switch=C {Case:C}

start process
  do Case;
end process

Maybe there already is and i am just lost on howto?

[toc] | [prev] | [next] | [standalone]

#36876

Den torsdag 13 juni 2019 kl. 09:49:39 UTC+2 skrev Jonas Thörnvall:
> Den torsdag 13 juni 2019 kl. 08:57:06 UTC+2 skrev Jonas Thörnvall:
> > Den torsdag 13 juni 2019 kl. 00:45:19 UTC+2 skrev Evertjan.:
> > > =?UTF-8?Q?Jonas_Th=C3=B6rnvall?= <jonas.thornvall@gmail.com> wrote on 12
> > > Jun 2019 in comp.lang.javascript: 
> > > 
> > > > I have a problem that i should know howto solve it is probably very
> > > > basic. 
> > > > 
> > > > Normally when you have choices, the most common way is to solve it with
> > > > if, else if. 
> > > > 
> > > > But sometimes your choices is fundamental to a process, so they are the
> > > > input parmeters for something. 
> > > > 
> > > > In my case i have a metronome, but depending on the "synth/hardware" you
> > > > want to use you simply select it from an option list. 
> > > > 
> > > > And now i could do 
> > > > 
> > > > if (met=="external") {something sent to port)
> > > > else if (met=="othersynth") {something else sent to port}
> > > > else if (met=="anothersynth") {something else sent to port}
> > > > 
> > > > 
> > > > If these are timed events it is not that effective to do this x times a
> > > > second. 
> > > > 
> > > > So you just want check and set the case once? and then be used everytime
> > > > during the interval? 
> > > > 
> > > > I guess that means to breakout the if cases into functions?
> > > > But you just want the actual function call to differ, but not be checked
> > > > every time you send something to the metronome. 
> > > > 
> > > > Basicly about setting what function to be called once, like flipping a
> > > > switch and then it always take that "path". 
> > > > 
> > > > I have a slight memory it could be case programming using switches, but
> > > > i don't quite see hot it applies dealing with timed events during an
> > > > interval? 
> > > > 
> > > > Basicly i want to replace if else if before every metronome event.
> > > 
> > > Basically you are not making sense,
> > > even for one professing a slight memory. 
> > > 
> > > Your timing requirements ar by large not short enough 
> > > to require machine language decision speeds.
> > > 
> > > Scripting language witches internally are just if-else-then constructs,
> > > and are perfect to implement logic showing a clearer human visible script, 
> > > not for much faster execution.
> > > 
> > > -- 
> > > Evertjan.
> > > The Netherlands.
> > > (Please change the x'es to dots in my emailaddress)
> > 
> > Even if it is not necessary in my case, is there a construct to handle this type of problems in Javascript? It must be something with realtime switches of sort.
> > 
> > It seem analogue to setting a switch to chose a leg/route "before" the actual timed events take place?
> > 
> > Is there a typecase for howto solve these types of problems?
> > Because i am a bit stumped for how i should tackle this type of problem?
> > They seem to create full legs with much more code then the actual choice of metronome? I could solve this type of problem with alot of code duplicated, but there must be some construct to just handle the explicit choice of metronome?
> 
> I guess this is maybe also about programming language methodology?
> 
> What would been awesome in languages would be...."i just dealt with highlevel Turbo Pascal, a little C , Java and javascript
> 
> A construct? like this.
> 
> Case A {do this}
> Case B {do that}
> Case C {do something else}
> 
> If switch=A {Case:A)} else if switch=B {Case:B)}elseif switch=C {Case:C}
> 
> start process
>   do Case;
> end process
> 
> Maybe there already is and i am just lost on howto?

I guess that Case  in my example is a variable / construct holding an adress to some code to be run?

[toc] | [prev] | [next] | [standalone]

#36881

On 13.06.19 09:57, Jonas Thörnvall wrote:

[Many many other posts]
> I guess that Case  in my example is a variable / construct holding an
> adress to some code to be run?


PLEASE! Think first about your problem before you ask. It makes no sense
to send seven(!) posts with your own thoughts. This indicates that you
may not even know what your real problem is what you want to solve.


-- 
Arno Welzel
https://arnowelzel.de

[toc] | [prev] | [next] | [standalone]

#36885

Den torsdag 13 juni 2019 kl. 11:31:44 UTC+2 skrev Arno Welzel:
> On 13.06.19 09:57, Jonas Thörnvall wrote:
> 
> [Many many other posts]
> > I guess that Case  in my example is a variable / construct holding an
> > adress to some code to be run?
> 
> 
> PLEASE! Think first about your problem before you ask. It makes no sense
> to send seven(!) posts with your own thoughts. This indicates that you
> may not even know what your real problem is what you want to solve.
> 
> 
> -- 
> Arno Welzel
> https://arnowelzel.de

Evertjan Quote: Scripting language witches internally are just if-else-then constructs, 
and are perfect to implement logic showing a clearer human visible script, 
not for much faster execution.

[toc] | [prev] | [next] | [standalone]

#36886

Den torsdag 13 juni 2019 kl. 11:31:44 UTC+2 skrev Arno Welzel:
> On 13.06.19 09:57, Jonas Thörnvall wrote:
> 
> [Many many other posts]
> > I guess that Case  in my example is a variable / construct holding an
> > adress to some code to be run?
> 
> 
> PLEASE! Think first about your problem before you ask. It makes no sense
> to send seven(!) posts with your own thoughts. This indicates that you
> may not even know what your real problem is what you want to solve.
> 
> 
> -- 
> Arno Welzel
> https://arnowelzel.de

So was Evertjan wrong?, joking? or is my question still valid and unanswered?

[toc] | [prev] | [next] | [standalone]

#36888

Den torsdag 13 juni 2019 kl. 11:31:44 UTC+2 skrev Arno Welzel:
> On 13.06.19 09:57, Jonas Thörnvall wrote:
> 
> [Many many other posts]
> > I guess that Case  in my example is a variable / construct holding an
> > adress to some code to be run?
> 
> 
> PLEASE! Think first about your problem before you ask. It makes no sense
> to send seven(!) posts with your own thoughts. This indicates that you
> may not even know what your real problem is what you want to solve.
> 
> 
> -- 
> Arno Welzel
> https://arnowelzel.de

I think i found the difference between if else if and switch. It seem that if else if do not break when found, so if there is many else if still steps thru?

While the switch "do indeed check sequential the cases until found and break" ***well if i understand correct***

But i think Evertjan is correct switch do an evaluation?

Quote google "As it turns out, the switch statement is faster in most cases when compared to if-else , but significantly faster only when the number of conditions is large. The primary difference in performance between the two is that the incremental cost of an additional condition is larger for if-else than" it is for switch .

[toc] | [prev] | [next] | [standalone]

#36901

On 13.06.19 12:26, Jonas Thörnvall wrote:

> Den torsdag 13 juni 2019 kl. 11:31:44 UTC+2 skrev Arno Welzel:
>> On 13.06.19 09:57, Jonas Thörnvall wrote:
>> 
>> [Many many other posts]
>>> I guess that Case  in my example is a variable / construct
>>> holding an adress to some code to be run?
>> 
>> 
>> PLEASE! Think first about your problem before you ask. It makes no
>> sense to send seven(!) posts with your own thoughts. This indicates
>> that you may not even know what your real problem is what you want
>> to solve.
>> 
>> 
>> -- Arno Welzel https://arnowelzel.de
> 
> I think i found the difference between if else if and switch. It seem
> that if else if do not break when found, so if there is many else if
> still steps thru?
[...]

Again - THREE posts. Why? I don't answer any of them any longer, since I
have to expect, that another 5 to 10 posts follow just right to the one
which was answered...



-- 
Arno Welzel
https://arnowelzel.de

[toc] | [prev] | [next] | [standalone]

#36880

On 13.06.19 09:49, Jonas Thörnvall wrote:

> A construct? like this.
> 
> Case A {do this}
> Case B {do that}
> Case C {do something else}

<https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/switch>



-- 
Arno Welzel
https://arnowelzel.de

[toc] | [prev] | [next] | [standalone]

#36883

Den torsdag 13 juni 2019 kl. 11:29:18 UTC+2 skrev Arno Welzel:
> On 13.06.19 09:49, Jonas Thörnvall wrote:
> 
> > A construct? like this.
> > 
> > Case A {do this}
> > Case B {do that}
> > Case C {do something else}
> 
> <https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/switch>
> 
> 
> 
> -- 
> Arno Welzel
> https://arnowelzel.de

Well Arno Evertjan claimed that javscript switch is just a fancy layout and doing if else if in background. So it is just a reading aid for code.

But maybe he was just trying to pull a joke upon me.

[toc] | [prev] | [next] | [standalone]

#36887

=?UTF-8?Q?Jonas_Th=C3=B6rnvall?= <jonas.thornvall@gmail.com> wrote on 13
Jun 2019 in comp.lang.javascript: 

> Well Arno Evertjan claimed that javscript switch is just a fancy layout
> and doing if else if in background. So it is just a reading aid for
> code. 

No, you should not try to read between the lines.

A switch DOES the same in the background as a if-then-else construct does,
but IS NOT the same.

You can easily measure any timing improvement by setting up a test script.

> But maybe he was just trying to pull a joke upon me.

This is the first sensible idea you have, 
you should always be prepared for that.

After all, forgetting the sex thing, there is only one thing more enjoyable 
than discussing by arguments, and that is exchanging jokes.

PS: the discussion being more educational.

-- 
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)

[toc] | [prev] | [next] | [standalone]

#36890

Den torsdag 13 juni 2019 kl. 12:24:42 UTC+2 skrev Evertjan.:
> =?UTF-8?Q?Jonas_Th=C3=B6rnvall?= <jonas.thornvall@gmail.com> wrote on 13
> Jun 2019 in comp.lang.javascript: 
> 
> > Well Arno Evertjan claimed that javscript switch is just a fancy layout
> > and doing if else if in background. So it is just a reading aid for
> > code. 
> 
> No, you should not try to read between the lines.
> 
> A switch DOES the same in the background as a if-then-else construct does,
> but IS NOT the same.
> 
> You can easily measure any timing improvement by setting up a test script.
> 
> > But maybe he was just trying to pull a joke upon me.
> 
> This is the first sensible idea you have, 
> you should always be prepared for that.
> 
> After all, forgetting the sex thing, there is only one thing more enjoyable 
> than discussing by arguments, and that is exchanging jokes.
> 
> PS: the discussion being more educational.
> 
> -- 
> Evertjan.
> The Netherlands.
> (Please change the x'es to dots in my emailaddress)

Well you make me confused Evertjan is there a sequential case evaluation until break, or is case basicly a function call to the appropriate case?

If it is not, why does not javascript have a construct more like this pseudocode where Case basicly a variable assigned to hold a function call?

Case A {do this} 
Case B {do that} 
Case C {do something else} 

If switch=A {Case:A)} else if switch=B {Case:B)}elseif switch=C {Case:C} 

start process 
  do Case; 
end process 

[toc] | [prev] | [next] | [standalone]

#36891

Den torsdag 13 juni 2019 kl. 12:36:51 UTC+2 skrev Jonas Thörnvall:
> Den torsdag 13 juni 2019 kl. 12:24:42 UTC+2 skrev Evertjan.:
> > =?UTF-8?Q?Jonas_Th=C3=B6rnvall?= <jonas.thornvall@gmail.com> wrote on 13
> > Jun 2019 in comp.lang.javascript: 
> > 
> > > Well Arno Evertjan claimed that javscript switch is just a fancy layout
> > > and doing if else if in background. So it is just a reading aid for
> > > code. 
> > 
> > No, you should not try to read between the lines.
> > 
> > A switch DOES the same in the background as a if-then-else construct does,
> > but IS NOT the same.
> > 
> > You can easily measure any timing improvement by setting up a test script.
> > 
> > > But maybe he was just trying to pull a joke upon me.
> > 
> > This is the first sensible idea you have, 
> > you should always be prepared for that.
> > 
> > After all, forgetting the sex thing, there is only one thing more enjoyable 
> > than discussing by arguments, and that is exchanging jokes.
> > 
> > PS: the discussion being more educational.
> > 
> > -- 
> > Evertjan.
> > The Netherlands.
> > (Please change the x'es to dots in my emailaddress)
> 
> Well you make me confused Evertjan is there a sequential case evaluation until break, or is case basicly a function call to the appropriate case?
> 
> If it is not, why does not javascript have a construct more like this pseudocode where Case basicly a variable assigned to hold a function call?
> 
> Case A {do this} 
> Case B {do that} 
> Case C {do something else} 
> 
> If switch=A {Case:A)} else if switch=B {Case:B)}elseif switch=C {Case:C} 
> 
> start process 
>   do Case; 
> end process

This syntax would probably be more suitable for javascript.

 Case(A) {do this} 
 Case(B) {do that} 
 Case(C) {do something else} 
 
 If (switch==A) {x=A)} else if (switch==B) {x=B)} elseif (switch==C) {x=C} 
 
 
 setTimeout(function(){Case(x);}, 300);

Well i know that x is normally a function parameter, and there is no syntax appropriate but since Case probably a reserved word i see no problem with it.

I think it is rather beautiful in its simplicity?
 

[toc] | [prev] | [next] | [standalone]

#36893

Den torsdag 13 juni 2019 kl. 12:48:45 UTC+2 skrev Jonas Thörnvall:
> Den torsdag 13 juni 2019 kl. 12:36:51 UTC+2 skrev Jonas Thörnvall:
> > Den torsdag 13 juni 2019 kl. 12:24:42 UTC+2 skrev Evertjan.:
> > > =?UTF-8?Q?Jonas_Th=C3=B6rnvall?= <jonas.thornvall@gmail.com> wrote on 13
> > > Jun 2019 in comp.lang.javascript: 
> > > 
> > > > Well Arno Evertjan claimed that javscript switch is just a fancy layout
> > > > and doing if else if in background. So it is just a reading aid for
> > > > code. 
> > > 
> > > No, you should not try to read between the lines.
> > > 
> > > A switch DOES the same in the background as a if-then-else construct does,
> > > but IS NOT the same.
> > > 
> > > You can easily measure any timing improvement by setting up a test script.
> > > 
> > > > But maybe he was just trying to pull a joke upon me.
> > > 
> > > This is the first sensible idea you have, 
> > > you should always be prepared for that.
> > > 
> > > After all, forgetting the sex thing, there is only one thing more enjoyable 
> > > than discussing by arguments, and that is exchanging jokes.
> > > 
> > > PS: the discussion being more educational.
> > > 
> > > -- 
> > > Evertjan.
> > > The Netherlands.
> > > (Please change the x'es to dots in my emailaddress)
> > 
> > Well you make me confused Evertjan is there a sequential case evaluation until break, or is case basicly a function call to the appropriate case?
> > 
> > If it is not, why does not javascript have a construct more like this pseudocode where Case basicly a variable assigned to hold a function call?
> > 
> > Case A {do this} 
> > Case B {do that} 
> > Case C {do something else} 
> > 
> > If switch=A {Case:A)} else if switch=B {Case:B)}elseif switch=C {Case:C} 
> > 
> > start process 
> >   do Case; 
> > end process
> 
> This syntax would probably be more suitable for javascript.
> 
>  Case(A) {do this} 
>  Case(B) {do that} 
>  Case(C) {do something else} 
>  
>  If (switch==A) {x=A)} else if (switch==B) {x=B)} elseif (switch==C) {x=C} 
>  
>  
>  setTimeout(function(){Case(x);}, 300);
> 
> Well i know that x is normally a function parameter, and there is no syntax appropriate but since Case probably a reserved word i see no problem with it.
> 
> I think it is rather beautiful in its simplicity?

So the string value of x decide case it will chose?

[toc] | [prev] | [next] | [standalone]

#36894

Den torsdag 13 juni 2019 kl. 12:48:45 UTC+2 skrev Jonas Thörnvall:
> Den torsdag 13 juni 2019 kl. 12:36:51 UTC+2 skrev Jonas Thörnvall:
> > Den torsdag 13 juni 2019 kl. 12:24:42 UTC+2 skrev Evertjan.:
> > > =?UTF-8?Q?Jonas_Th=C3=B6rnvall?= <jonas.thornvall@gmail.com> wrote on 13
> > > Jun 2019 in comp.lang.javascript: 
> > > 
> > > > Well Arno Evertjan claimed that javscript switch is just a fancy layout
> > > > and doing if else if in background. So it is just a reading aid for
> > > > code. 
> > > 
> > > No, you should not try to read between the lines.
> > > 
> > > A switch DOES the same in the background as a if-then-else construct does,
> > > but IS NOT the same.
> > > 
> > > You can easily measure any timing improvement by setting up a test script.
> > > 
> > > > But maybe he was just trying to pull a joke upon me.
> > > 
> > > This is the first sensible idea you have, 
> > > you should always be prepared for that.
> > > 
> > > After all, forgetting the sex thing, there is only one thing more enjoyable 
> > > than discussing by arguments, and that is exchanging jokes.
> > > 
> > > PS: the discussion being more educational.
> > > 
> > > -- 
> > > Evertjan.
> > > The Netherlands.
> > > (Please change the x'es to dots in my emailaddress)
> > 
> > Well you make me confused Evertjan is there a sequential case evaluation until break, or is case basicly a function call to the appropriate case?
> > 
> > If it is not, why does not javascript have a construct more like this pseudocode where Case basicly a variable assigned to hold a function call?
> > 
> > Case A {do this} 
> > Case B {do that} 
> > Case C {do something else} 
> > 
> > If switch=A {Case:A)} else if switch=B {Case:B)}elseif switch=C {Case:C} 
> > 
> > start process 
> >   do Case; 
> > end process
> 
> This syntax would probably be more suitable for javascript.
> 
>  Case(A) {do this} 
>  Case(B) {do that} 
>  Case(C) {do something else} 
>  
>  If (switch==A) {x=A)} else if (switch==B) {x=B)} elseif (switch==C) {x=C} 
>  
>  
>  setTimeout(function(){Case(x);}, 300);
> 
> Well i know that x is normally a function parameter, and there is no syntax appropriate but since Case probably a reserved word i see no problem with it.
> 
> I think it is rather beautiful in its simplicity?

Well maybe you lke this syntax better.

 Case:A {do this} 
 Case:B {do that} 
 Case:C {do something else} 
  
 If (switch==A) {x=A)} else if (switch==B) {x=B)} elseif (switch==C) {x=C} 
  
  
 setTimeout(function(){Case:(x);}, 300)

[toc] | [prev] | [next] | [standalone]

#36895

Den torsdag 13 juni 2019 kl. 13:01:26 UTC+2 skrev Jonas Thörnvall:
> Den torsdag 13 juni 2019 kl. 12:48:45 UTC+2 skrev Jonas Thörnvall:
> > Den torsdag 13 juni 2019 kl. 12:36:51 UTC+2 skrev Jonas Thörnvall:
> > > Den torsdag 13 juni 2019 kl. 12:24:42 UTC+2 skrev Evertjan.:
> > > > =?UTF-8?Q?Jonas_Th=C3=B6rnvall?= <jonas.thornvall@gmail.com> wrote on 13
> > > > Jun 2019 in comp.lang.javascript: 
> > > > 
> > > > > Well Arno Evertjan claimed that javscript switch is just a fancy layout
> > > > > and doing if else if in background. So it is just a reading aid for
> > > > > code. 
> > > > 
> > > > No, you should not try to read between the lines.
> > > > 
> > > > A switch DOES the same in the background as a if-then-else construct does,
> > > > but IS NOT the same.
> > > > 
> > > > You can easily measure any timing improvement by setting up a test script.
> > > > 
> > > > > But maybe he was just trying to pull a joke upon me.
> > > > 
> > > > This is the first sensible idea you have, 
> > > > you should always be prepared for that.
> > > > 
> > > > After all, forgetting the sex thing, there is only one thing more enjoyable 
> > > > than discussing by arguments, and that is exchanging jokes.
> > > > 
> > > > PS: the discussion being more educational.
> > > > 
> > > > -- 
> > > > Evertjan.
> > > > The Netherlands.
> > > > (Please change the x'es to dots in my emailaddress)
> > > 
> > > Well you make me confused Evertjan is there a sequential case evaluation until break, or is case basicly a function call to the appropriate case?
> > > 
> > > If it is not, why does not javascript have a construct more like this pseudocode where Case basicly a variable assigned to hold a function call?
> > > 
> > > Case A {do this} 
> > > Case B {do that} 
> > > Case C {do something else} 
> > > 
> > > If switch=A {Case:A)} else if switch=B {Case:B)}elseif switch=C {Case:C} 
> > > 
> > > start process 
> > >   do Case; 
> > > end process
> > 
> > This syntax would probably be more suitable for javascript.
> > 
> >  Case(A) {do this} 
> >  Case(B) {do that} 
> >  Case(C) {do something else} 
> >  
> >  If (switch==A) {x=A)} else if (switch==B) {x=B)} elseif (switch==C) {x=C} 
> >  
> >  
> >  setTimeout(function(){Case(x);}, 300);
> > 
> > Well i know that x is normally a function parameter, and there is no syntax appropriate but since Case probably a reserved word i see no problem with it.
> > 
> > I think it is rather beautiful in its simplicity?
> 
> Well maybe you lke this syntax better.
> 
>  Case:A {do this} 
>  Case:B {do that} 
>  Case:C {do something else} 
>   
>  If (switch==A) {x=A)} else if (switch==B) {x=B)} elseif (switch==C) {x=C} 
>   
>   
>  setTimeout(function(){Case:(x);}, 300)

Of course this is all my personal preferences but it is fucking simple...

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | comp.lang.javascript

csiph-web