Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. The Lounge
  3. Friday Programming Quiz [modified]

Friday Programming Quiz [modified]

Scheduled Pinned Locked Moved The Lounge
c++csharppythoncomdata-structures
21 Posts 8 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • R Robert Rohde

    Hi, what do you think of this solution?

    void ExecuteActions(Action[] actions, ActionComplete onAllActionsComplete)
    {
    for (int i = 0; i < actions.Length; i++)
    {
    ManualResetEvent mre = new ManualResetEvent(false);
    actions[i](delegate() { mre.Set(); });
    mre.WaitOne();
    }
    onAllActionsComplete();
    }

    Robert

    R Offline
    R Offline
    Rama Krishna Vavilala
    wrote on last edited by
    #5

    :cool:This will work too. :) BTW: This is not really the most efficient thing to do but the point of this quiz is to have fun and not to develop an efficent solution.


    Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -Brian Kernighan

    R 1 Reply Last reply
    0
    • R Robert Rohde

      Hi, what do you think of this solution?

      void ExecuteActions(Action[] actions, ActionComplete onAllActionsComplete)
      {
      for (int i = 0; i < actions.Length; i++)
      {
      ManualResetEvent mre = new ManualResetEvent(false);
      actions[i](delegate() { mre.Set(); });
      mre.WaitOne();
      }
      onAllActionsComplete();
      }

      Robert

      R Offline
      R Offline
      Rama Krishna Vavilala
      wrote on last edited by
      #6

      Actually you can also do this:

      void ExecuteActions(Action[] actions, ActionComplete onAllActionsComplete)
      {
      AutoResetEvent are = new AutoResetEvent(false);
      for (int i = 0; i < actions.Length; i++)
      {
      actions[i](delegate() { are.Set(); });
      are.WaitOne();
      }

      onAllActionsComplete();
      }


      Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -Brian Kernighan

      1 Reply Last reply
      0
      • R Rama Krishna Vavilala

        As currently I am working on asynchronous programming (and my mind is spinning), this quiz is about a simple async programming problem. Given:

        //C# delegates
        delegate void ActionComplete();
        delegate void Action(ActionComplete onComplete);

        Functions conforming to Action execute asynchronously and invoke the function supplied in the onComplete parameter when complete. For Example, the following ProcessReport function conforms to the delegate Action.

        void ProcessReport(ActionComplete onReportProcessed)
        {
        //Start a thread to do actual processing and return
        //Call onReportProcessed from the thread when processing is done
        }

        Now the real problem: You have a an array of such asynchronous functions and the objective is to execute them one by one in order and call a callback when all the functions have finished executing.

        void ExecuteActions(Action[] actions, ActionComplete onAllActionsComplete)
        {
        }

        onAllActionsComplete should be called only once when all the actions have finished executing in order. If there are 3 actions, onAllActionsComplete should be called when actions[2] completes, actions[2] should start after actions[1] completes, actions[1] should start when actions[0] completes. actions[0] should start first. -------------------------------------- Here is a C++ STL solution to last weeks quiz[^]. It is almost as simple as the python or haskell solution.

        bool SameSetOfCharacters(string str1, string str2)
        {
        typedef CharSet std::set<char>;
        return CharSet(str1.begin(), str1.end()) == CharSet(str2.begin(), str2.end());
        }

        -- modified at 16:57 Friday 17th November, 2006


        Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -Brian Kernighan

        M Offline
        M Offline
        Matt Gerrans
        wrote on last edited by
        #7

        Hey, wait a minute! Isn't this a programming question?

        Matt Gerrans

        N R 2 Replies Last reply
        0
        • R Rama Krishna Vavilala

          :cool:This will work too. :) BTW: This is not really the most efficient thing to do but the point of this quiz is to have fun and not to develop an efficent solution.


          Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -Brian Kernighan

          R Offline
          R Offline
          Robert Rohde
          wrote on last edited by
          #8

          Now I'm curious. Why would you say that this isn't efficient? Robert

          R 1 Reply Last reply
          0
          • M Matt Gerrans

            Hey, wait a minute! Isn't this a programming question?

            Matt Gerrans

            N Offline
            N Offline
            Nish Nishant
            wrote on last edited by
            #9

            Matt Gerrans wrote:

            Isn't this a programming question?

            It's sorta - but it's a new tradition. Respect it or weep. :-D

            Regards, Nish


            Nish’s thoughts on MFC, C++/CLI and .NET (my blog)
            Currently working on C++/CLI in Action for Manning Publications. (*Sample chapter available online*)

            1 Reply Last reply
            0
            • M Matt Gerrans

              Hey, wait a minute! Isn't this a programming question?

              Matt Gerrans

              R Offline
              R Offline
              Rama Krishna Vavilala
              wrote on last edited by
              #10

              Matt Gerrans wrote:

              Isn't this a programming question

              This is a programming quiz. The purpose is to have fun. The problems presented here are too trivial.


              Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -Brian Kernighan

              M 1 Reply Last reply
              0
              • R Rama Krishna Vavilala

                As currently I am working on asynchronous programming (and my mind is spinning), this quiz is about a simple async programming problem. Given:

                //C# delegates
                delegate void ActionComplete();
                delegate void Action(ActionComplete onComplete);

                Functions conforming to Action execute asynchronously and invoke the function supplied in the onComplete parameter when complete. For Example, the following ProcessReport function conforms to the delegate Action.

                void ProcessReport(ActionComplete onReportProcessed)
                {
                //Start a thread to do actual processing and return
                //Call onReportProcessed from the thread when processing is done
                }

                Now the real problem: You have a an array of such asynchronous functions and the objective is to execute them one by one in order and call a callback when all the functions have finished executing.

                void ExecuteActions(Action[] actions, ActionComplete onAllActionsComplete)
                {
                }

                onAllActionsComplete should be called only once when all the actions have finished executing in order. If there are 3 actions, onAllActionsComplete should be called when actions[2] completes, actions[2] should start after actions[1] completes, actions[1] should start when actions[0] completes. actions[0] should start first. -------------------------------------- Here is a C++ STL solution to last weeks quiz[^]. It is almost as simple as the python or haskell solution.

                bool SameSetOfCharacters(string str1, string str2)
                {
                typedef CharSet std::set<char>;
                return CharSet(str1.begin(), str1.end()) == CharSet(str2.begin(), str2.end());
                }

                -- modified at 16:57 Friday 17th November, 2006


                Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -Brian Kernighan

                P Offline
                P Offline
                PIEBALDconsult
                wrote on last edited by
                #11

                Well I won't even try that one. And I wonder why you would insist that they be asynchronous if you only run one at a time, I'll assume they are from some other developer. Hmmm... I expect even if they are you could wrap them in something to make them appear synchronous. What I do have though is... In my current project I have need of putting data into a third-party product for which the only interface I have is a character-based program on a Unix server. I have to telnet to the Unix server, login, execute the program, put in the data, exit the program, logout, and disconnect. And I need to do this for each "item" I need to put into the system (trying to put in more than one per session is problematic). So I want to have multiple threads, each entering one item, and I don't want to proceed until they're all done. I accomplished this with what I call a ThreadStack (although it's technically neither LIFO nor FIFO). The code isn't yet ready for Code Project, but if anyone is interested I can clean it up. I'll mention that I've had this solution running as a Windows service with up to ten simultaneous threads for the past year with no problems.

                1 Reply Last reply
                0
                • R Rama Krishna Vavilala

                  As currently I am working on asynchronous programming (and my mind is spinning), this quiz is about a simple async programming problem. Given:

                  //C# delegates
                  delegate void ActionComplete();
                  delegate void Action(ActionComplete onComplete);

                  Functions conforming to Action execute asynchronously and invoke the function supplied in the onComplete parameter when complete. For Example, the following ProcessReport function conforms to the delegate Action.

                  void ProcessReport(ActionComplete onReportProcessed)
                  {
                  //Start a thread to do actual processing and return
                  //Call onReportProcessed from the thread when processing is done
                  }

                  Now the real problem: You have a an array of such asynchronous functions and the objective is to execute them one by one in order and call a callback when all the functions have finished executing.

                  void ExecuteActions(Action[] actions, ActionComplete onAllActionsComplete)
                  {
                  }

                  onAllActionsComplete should be called only once when all the actions have finished executing in order. If there are 3 actions, onAllActionsComplete should be called when actions[2] completes, actions[2] should start after actions[1] completes, actions[1] should start when actions[0] completes. actions[0] should start first. -------------------------------------- Here is a C++ STL solution to last weeks quiz[^]. It is almost as simple as the python or haskell solution.

                  bool SameSetOfCharacters(string str1, string str2)
                  {
                  typedef CharSet std::set<char>;
                  return CharSet(str1.begin(), str1.end()) == CharSet(str2.begin(), str2.end());
                  }

                  -- modified at 16:57 Friday 17th November, 2006


                  Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -Brian Kernighan

                  M Offline
                  M Offline
                  Marc Clifton
                  wrote on last edited by
                  #12

                  Funny, I have a very similar problem to solve, with regards to re-encoding a movie into a different format, that must first be indexed, then multiple threads can run to actually encode the movie in different speed formats, and when all the encoding is done, the database is notified that the entire process is complete. And to make matters more interesting, the threads have to be prioritized so that certain encodes are done first, and the system optimizes encoding by creating one thread per CPU. Anyways, I ended up using a priority queue to generate the task list and then a separate process pulls tasks off and assigns them to processors. When the task is complete, the thread notifies the queue processor that it can assign a new task. In your particular case, I'd probably just wire up an event to notify a worker thread that the task was done, set up and an index for the first task, do the task, increment, do the next task, etc., then call the actions complete event. Marc

                  Thyme In The Country

                  People are just notoriously impossible. --DavidCrow
                  There's NO excuse for not commenting your code. -- John Simmons / outlaw programmer
                  People who say that they will refactor their code later to make it "good" don't understand refactoring, nor the art and craft of programming. -- Josh Smith

                  R 1 Reply Last reply
                  0
                  • R Robert Rohde

                    Now I'm curious. Why would you say that this isn't efficient? Robert

                    R Offline
                    R Offline
                    Rama Krishna Vavilala
                    wrote on last edited by
                    #13

                    Actually, efficent may have been a poor choice of word. I should have said not really the best solution. The problem is that one thread is used up by the wait handle and nothing can execute on that thread. For situations like ASP.NET where there are some set threads that work on request processing, a vital request processing thread will be used up just for waiting.


                    Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -Brian Kernighan

                    R 1 Reply Last reply
                    0
                    • M Marc Clifton

                      Funny, I have a very similar problem to solve, with regards to re-encoding a movie into a different format, that must first be indexed, then multiple threads can run to actually encode the movie in different speed formats, and when all the encoding is done, the database is notified that the entire process is complete. And to make matters more interesting, the threads have to be prioritized so that certain encodes are done first, and the system optimizes encoding by creating one thread per CPU. Anyways, I ended up using a priority queue to generate the task list and then a separate process pulls tasks off and assigns them to processors. When the task is complete, the thread notifies the queue processor that it can assign a new task. In your particular case, I'd probably just wire up an event to notify a worker thread that the task was done, set up and an index for the first task, do the task, increment, do the next task, etc., then call the actions complete event. Marc

                      Thyme In The Country

                      People are just notoriously impossible. --DavidCrow
                      There's NO excuse for not commenting your code. -- John Simmons / outlaw programmer
                      People who say that they will refactor their code later to make it "good" don't understand refactoring, nor the art and craft of programming. -- Josh Smith

                      R Offline
                      R Offline
                      Rama Krishna Vavilala
                      wrote on last edited by
                      #14

                      Actually my problem was in JavaScript/Ajax so I could not create threads. But it was fun to solve using anonymous functions and closures. PS I am sorry for hijacking the Friday Programming Quiz started by you.


                      Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -Brian Kernighan

                      M 1 Reply Last reply
                      0
                      • R Rama Krishna Vavilala

                        Actually, efficent may have been a poor choice of word. I should have said not really the best solution. The problem is that one thread is used up by the wait handle and nothing can execute on that thread. For situations like ASP.NET where there are some set threads that work on request processing, a vital request processing thread will be used up just for waiting.


                        Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -Brian Kernighan

                        R Offline
                        R Offline
                        Robert Rohde
                        wrote on last edited by
                        #15

                        Hi, if I understand you correctly one could overcome this problem by starting another thread where the waiting takes place. Thus the request processing thread won't be blocked. Nevertheless I agree that there is one thread more active than necessary. The best solution definitely depends on the context where the code is executed in. To be honest I also tried to just get the shortest solution I could think of. I think regarding this my code should be in the premier league :laugh:. Robert

                        R 1 Reply Last reply
                        0
                        • R Robert Rohde

                          Hi, if I understand you correctly one could overcome this problem by starting another thread where the waiting takes place. Thus the request processing thread won't be blocked. Nevertheless I agree that there is one thread more active than necessary. The best solution definitely depends on the context where the code is executed in. To be honest I also tried to just get the shortest solution I could think of. I think regarding this my code should be in the premier league :laugh:. Robert

                          R Offline
                          R Offline
                          Rama Krishna Vavilala
                          wrote on last edited by
                          #16

                          Robert Rohde wrote:

                          I think regarding this my code should be in the premier league .

                          Sure! So far it is the shortest. But the no-wait solution is also possible with probably same amount of code in LINQ/JavaScript. I want to see whether the LINQ Boy[^] or the JavaScript Man [^] to come up with it.


                          Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -Brian Kernighan

                          1 Reply Last reply
                          0
                          • R Rama Krishna Vavilala

                            As currently I am working on asynchronous programming (and my mind is spinning), this quiz is about a simple async programming problem. Given:

                            //C# delegates
                            delegate void ActionComplete();
                            delegate void Action(ActionComplete onComplete);

                            Functions conforming to Action execute asynchronously and invoke the function supplied in the onComplete parameter when complete. For Example, the following ProcessReport function conforms to the delegate Action.

                            void ProcessReport(ActionComplete onReportProcessed)
                            {
                            //Start a thread to do actual processing and return
                            //Call onReportProcessed from the thread when processing is done
                            }

                            Now the real problem: You have a an array of such asynchronous functions and the objective is to execute them one by one in order and call a callback when all the functions have finished executing.

                            void ExecuteActions(Action[] actions, ActionComplete onAllActionsComplete)
                            {
                            }

                            onAllActionsComplete should be called only once when all the actions have finished executing in order. If there are 3 actions, onAllActionsComplete should be called when actions[2] completes, actions[2] should start after actions[1] completes, actions[1] should start when actions[0] completes. actions[0] should start first. -------------------------------------- Here is a C++ STL solution to last weeks quiz[^]. It is almost as simple as the python or haskell solution.

                            bool SameSetOfCharacters(string str1, string str2)
                            {
                            typedef CharSet std::set<char>;
                            return CharSet(str1.begin(), str1.end()) == CharSet(str2.begin(), str2.end());
                            }

                            -- modified at 16:57 Friday 17th November, 2006


                            Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -Brian Kernighan

                            S Offline
                            S Offline
                            Shog9 0
                            wrote on last edited by
                            #17

                            As you suspected, this sort of thing is trivial in JS. Of course, it helps that JS is single-threaded, but functions as objects and closures make it even easier. Here's a quick-and-dirty (read: untested) solution:

                            function ExecuteActions(actions, onAllActionsComplete)
                            {
                            var loop = function(i)
                            {
                            if ( i < actions.length )
                            actions[i](function() { loop(i+1) });
                            else
                            onAllActionsComplete();
                            }
                            loop(0);
                            }

                            R 1 Reply Last reply
                            0
                            • S Shog9 0

                              As you suspected, this sort of thing is trivial in JS. Of course, it helps that JS is single-threaded, but functions as objects and closures make it even easier. Here's a quick-and-dirty (read: untested) solution:

                              function ExecuteActions(actions, onAllActionsComplete)
                              {
                              var loop = function(i)
                              {
                              if ( i < actions.length )
                              actions[i](function() { loop(i+1) });
                              else
                              onAllActionsComplete();
                              }
                              loop(0);
                              }

                              R Offline
                              R Offline
                              Rama Krishna Vavilala
                              wrote on last edited by
                              #18

                              Exactly, this is what I ended up implementing in JS (hence the quiz). :) BTW my version looked something like following:

                              function ExecuteActions(actions, onAllActionsComplete) {
                              var i = 0;
                              function nextAction() {
                              if ( i < actions.length )
                              actions[i++](nextAction);
                              else
                              onAllActionsComplete();
                              }
                              nextAction();
                              }


                              Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -Brian Kernighan

                              S 1 Reply Last reply
                              0
                              • R Rama Krishna Vavilala

                                Exactly, this is what I ended up implementing in JS (hence the quiz). :) BTW my version looked something like following:

                                function ExecuteActions(actions, onAllActionsComplete) {
                                var i = 0;
                                function nextAction() {
                                if ( i < actions.length )
                                actions[i++](nextAction);
                                else
                                onAllActionsComplete();
                                }
                                nextAction();
                                }


                                Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -Brian Kernighan

                                S Offline
                                S Offline
                                Shog9 0
                                wrote on last edited by
                                #19

                                I use something similar in CPhog for updating threads. Of course, i don't use K&R-style braces, so it's inherently better... ;P

                                1 Reply Last reply
                                0
                                • R Rama Krishna Vavilala

                                  Actually my problem was in JavaScript/Ajax so I could not create threads. But it was fun to solve using anonymous functions and closures. PS I am sorry for hijacking the Friday Programming Quiz started by you.


                                  Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -Brian Kernighan

                                  M Offline
                                  M Offline
                                  Marc Clifton
                                  wrote on last edited by
                                  #20

                                  Rama Krishna Vavilala wrote:

                                  I am sorry for hijacking the Friday Programming Quiz started by you.

                                  No need to apologize! You're doing a fantastic job! :) Marc

                                  Thyme In The Country

                                  People are just notoriously impossible. --DavidCrow
                                  There's NO excuse for not commenting your code. -- John Simmons / outlaw programmer
                                  People who say that they will refactor their code later to make it "good" don't understand refactoring, nor the art and craft of programming. -- Josh Smith

                                  1 Reply Last reply
                                  0
                                  • R Rama Krishna Vavilala

                                    Matt Gerrans wrote:

                                    Isn't this a programming question

                                    This is a programming quiz. The purpose is to have fun. The problems presented here are too trivial.


                                    Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -Brian Kernighan

                                    M Offline
                                    M Offline
                                    Matt Gerrans
                                    wrote on last edited by
                                    #21

                                    Sorry, I intended that to be a (good natured) parody of the Lounge posting police, but that apparently didn't work very well. :-O I do like the Programming Quiz and encourage you to continue! In fact, I'll provide a Python[^] (as usual) answer:

                                    def ExecuteActions( actions, onAllActionsComplete ):
                                    def doActions(actions):
                                    if actions:
                                    actions[0]( lambda: doActions(actions[1:]) )
                                    else:
                                    onAllActionsComplete()
                                    doActions(actions)

                                    (My first answer worked, but was a lot more clunky; this is what occurred to me after pondering it a bit more.) Also, here is the code to test drive it:

                                    def onAllActionsComplete():
                                    print 'onAllActionsComplete!'

                                    actions = []
                                    for l in 'abc':
                                    exec( 'def %s(o):\n\tprint "%s!"\n\to()\nactions.append(%s)' % ((l,)*3) )

                                    ExecuteActions( actions, onAllActionsComplete )

                                    (This could be made a little more terse by using lambda more, but that wouldn't necessarily be better.) By the way, thanks to IronPython[^], this would be an easy way to do it in .NET.

                                    Matt Gerrans

                                    1 Reply Last reply
                                    0
                                    Reply
                                    • Reply as topic
                                    Log in to reply
                                    • Oldest to Newest
                                    • Newest to Oldest
                                    • Most Votes


                                    • Login

                                    • Don't have an account? Register

                                    • Login or register to search.
                                    • First post
                                      Last post
                                    0
                                    • Categories
                                    • Recent
                                    • Tags
                                    • Popular
                                    • World
                                    • Users
                                    • Groups