Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Programming Puzzle 23 - For / Next Loop

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Programming Puzzle 23 - For / Next Loop

    Write an xbasic script that solves this puzzle using a For / Next loop. Include comments so the "professor" can figure out what you're doing without losing any more of his quickly disappearing hair! Display your result in a message box on screen. For extra credit write your result to the trace window, too.

    Puzzle 23:

    Jennifer arranged for a party and had a basket of strawberries to serve. She ate 5 strawberries before the party began, and gave a friend 3 more. Eight girls came to the party. The first girl took one strawberry. The second girl took three. The third girl took five, and so on. Her basket was empty after the last girl took hers. So, how many strawberries did she start with?

    Have fun!




    Puzzle courtesy easycalculation.com

  • #2
    Re: Programming Puzzle 23 - For / Next Loop

    Answer is "enough"
    Attached Files
    Andrew

    Comment


    • #3
      Re: Programming Puzzle 23 - For / Next Loop

      Very nice, Andrew!

      Professor Pickypicky asked me to remind you that you can't always count on Alpha Five to convert your data types for you. At line 38 you pass a numeric value to an argument in the ui_msg_box() function that is expecting a text string. In this case Alpha autoconverts your numeric to character data so the msg box does not fail. You cannot always count on autoconvert to correct data type mismatches. The professor thinks a better approach would be to convert the numeric value to a string of characters and pass that string to the msg box.

      The professor was wondering, also, whether you can think of a way to populate array elements 3 through 10 using a loop, to avoid having to repeat the same code over and over... ? The professor's intern wants to know something else... is there some way to compute the sum for the 8 "partiers" using a For .. Next loop that does not involve an array ? If so, maybe that would be a tiny bit more efficient.

      Thanks for playing!

      -- tom

      Comment


      • #4
        Re: Programming Puzzle 23 - For / Next Loop

        Second attempt
        Attached Files
        Andrew

        Comment


        • #5
          Re: Programming Puzzle 23 - For / Next Loop

          Sweet!

          Comment


          • #6
            Re: Programming Puzzle 23 - For / Next Loop

            Answer: Puzzle 23.txt

            I'd be interested to find an example of showing the result in the trace window grammatically. I attempted using debug(1) and trace.write(), but to see the value of the variables, had to enter them in the debug screen.

            Comment


            • #7
              Re: Programming Puzzle 23 - For / Next Loop

              Tony,

              Add this to the end of your script.

              Then run the script, then open Trace Window from the View Menu.

              Code:
              ' tom's code follows:
              
              dim vc_berries_count as C = ""   ' initialize character value variable
              vc_berries_count = ltrim(str(Stawberries_taken,10))   'convert numeric to string, trim leading blanks
              
              ' display in trace window
              trace.writeln("Jennifer started with " + vc_berries_count + " strawberries.")

              Comment


              • #8
                Re: Programming Puzzle 23 - For / Next Loop

                Thanks Tom,

                Turns out that I didn't know what the Trace Window was. That will be helpful going forward.

                I'm curious about why you create a type=C variable rather than allowing A5 to handle the conversion through context here. Is this a momentum and/or comfort and/or "haven't sufficiently tested the new thing" thing, or do you understand there to be perils in using the context based conversion?

                Comment


                • #9
                  Re: Programming Puzzle 23 - For / Next Loop

                  There is potential for perils in context conversion of data types.

                  Some languages I have used you had to explicitly convert the data types to use them in a different context. So for some this is a hold over of having to it manually. For others it is done to make sure issues do not occur in the future.

                  For me, I try to always convert the data types instead of having Alpha5 do it, but sometimes I get lazy and/or forget.
                  Andrew

                  Comment


                  • #10
                    Re: Programming Puzzle 23 - For / Next Loop

                    Tony, I explicitly convert all data types as a matter of course. In part this is because I don't know the "limits" for the built in auto-conversion routines. Do they work in all contexts? For all data types? I don't know. Guess I'm too lazy to figure it out. I also think that handling this explicitly simplifies debugging. If I screw up the data conversion I see it right away and can fix it. If Alpha screws up the data conversion the trail to the problem is not as clearly marked.

                    And, yes, the trace window is a very very handy tool. The professor thinks maybe its underutilized, so that's why she frequently offers extra credit for solutions displayed there.

                    Comment

                    Working...
                    X