• 0

How do i write this pseudocode?


Question

Hi guys,

I'm currently working on writing a psuedocode which would show a list of total sales between any two dates.

Here is what I came up with thus far:

Use Variables: Date 1, Date 2 of Type Integer

Sales, Total Sales of Type Real

Begin

Display ?Enter Start Date?

Accept Date 1

Display ?Enter End Date?

Accept Date 2

For (Date 1>=Start Date, Date 2<=End Date, +1)

Accept Sales

Total Sales:= Total Sales + Sales

End For

Print Total Sales

End

Am I going about this in the right manner? Was the For loop the correct method to use? I would appreciate any advice or suggestions. :)

Link to comment
https://www.neowin.net/forum/topic/917096-how-do-i-write-this-pseudocode/
Share on other sites

9 answers to this question

Recommended Posts

  • 0

A good approach is to write your pseudo code as potential comments or instructions for writing code, not using code, but plain english to save duplication. You then comment out each line as write the appropriate line of code, self documenting if you will.

for each user in user collection
allow user access to repo
then save

would become...

&lt;?php
#for each user in user collection
foreach($usercollection as $user){
	#allow user access to repo
	$user-&gt;allow('repo', true);
	#then save
	$user-&gt;save();
}
?&gt;

  • 0
  On 05/07/2010 at 11:26, AnthonySterling said:

A good approach is to write your pseudo code as potential comments or instructions for writing code, not using code, but plain english to save duplication. You then comment out each line as write the appropriate line of code, self documenting if you will.

for each user in user collection
allow user access to repo
then save

would become...

&lt;?php
#for each user in user collection
foreach($usercollection as $user){
	#allow user access to repo
	$user-&gt;allow('repo', true);
	#then save
	$user-&gt;save();
}
?&gt;

Writing instructions this way could help you and others know what the potential code will do once it is written. A good advice.

Just try to keep them as simple as possible.

  • 0
  On 05/07/2010 at 11:26, AnthonySterling said:

A good approach is to write your pseudo code as potential comments or instructions for writing code, not using code, but plain english to save duplication. You then comment out each line as write the appropriate line of code, self documenting if you will.

for each user in user collectionallow user access to repothen save

would become...

&lt;?php#for each user in user collectionforeach($usercollection as $user){	#allow user access to repo	$user-&gt;allow('repo', true);	#then save	$user-&gt;save();}?&gt;

This is acceptable practice for when you are first beginning to program. Do not do this when you get beyond introductory stuff. You will end up annoying experienced developers far more than you will be helping them. Wading through twice as many lines of code because someone likes to include commenting gems like the following is annoying, and not nearly as helpful as the likely well intentioned author probably meant them to be.

Bad:

// increment integer i by 1
i = i + 1
// remove Item from a list using remove() method.
list.remove(Item)

Also not good (because it is self-explanatory by glancing at the logic):

&lt;?php
#for each user in user collection
foreach($usercollection as $user){
        #allow user access to repo
        $user-&gt;allow('repo', true);
        #then save
        $user-&gt;save();
}
?&gt;

Basically, you don't want to be wasting your time while coding and someone elses time while maintaining, by commenting very obvious things especially on a line-by-line basis. Documenting code is an art. Doing it by simply replacing line-by-line the pseudo-code/notes/whatever with actual code is a terrible practice to get into. A good comment should succinctly explain the purpose of the a chunk of logic, give a brief overview of what is occurring, document any pre-conditions or post-conditions, and in general be summary of what the code is doing without unnecessary verbosity.

However, there is a time and a place to comment line-by-line. If you have some truly obscure algorithm stuff going on then it is necessary. Similarly, if you have a complicated Regex rule then it is also extremely helpful. These are all edge cases though.

  • Like 2
  • 0
  On 04/07/2010 at 17:13, DaMiEn said:

Hi guys,

I'm currently working on writing a psuedocode which would show a list of total sales between any two dates.

Here is what I came up with thus far:

Use Variables: Date 1, Date 2 of Type Integer

Sales, Total Sales of Type Real

Begin

Display ?Enter Start Date?

Accept Date 1

Display ?Enter End Date?

Accept Date 2

For (Date 1>=Start Date, Date 2<=End Date, +1)

Accept Sales

Total Sales:= Total Sales + Sales

End For

Print Total Sales

End

Am I going about this in the right manner? Was the For loop the correct method to use? I would appreciate any advice or suggestions. :)

Why Date1 AND Date2 controlling the For loop ?

Usually it's just one variable, and it gets incremented until the second condition is no longer true..

i.e. Date 1 <= End Date, instead of Date 2 <= End Date

  • 0
  On 04/07/2010 at 17:13, DaMiEn said:

Hi guys,

I'm currently working on writing a psuedocode which would show a list of total sales between any two dates.

Here is what I came up with thus far:

Use Variables: Date 1, Date 2 of Type Integer

Sales, Total Sales of Type Real

Begin

Display ?Enter Start Date?

Accept Date 1

Display ?Enter End Date?

Accept Date 2

For (Date 1>=Start Date, Date 2<=End Date, +1)

Accept Sales

Total Sales:= Total Sales + Sales

End For

Print Total Sales

End

Am I going about this in the right manner? Was the For loop the correct method to use? I would appreciate any advice or suggestions. :)

This problem requires a set operation, and it wouldn't make sense to use a for loop. If anything, you'd use a while loop provided that all the records are sorted by "sales date".

The pseudo code would look something like this:

Begin

Display ?Enter Start Date?

Accept Date 1

Display ?Enter End Date?

Accept Date 2

Sort SalesRecords by Sales Date Ascending

Found := false

While Not EOF(SalesRecords)

If (Sales Date >= Date 1)

Found:= true

End If

Next SalesRecord

End While

If Found = false

Print 0

Return

End If

Total Sales := 0

While Sales Date <= Date 2 And Not EOF(SalesRecords)

Total Sales := Total Sales + Sales

Next SalesRecord

End While

Print Total Sales

End

BTW, this is the kind of use case that a technology like Microsoft's LINQ turns into a triviality:

var totalsales = dc.Sales.Where(x => x.SalesDate >= Date1 && x.SalesDate < Date2.AddDays(1)).Sum(x => x.SalesAmount);

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Linus Torvalds releases a pretty ordinary Linux 6.16-rc3 by Paul Hill Linus Torvalds, the head and founder of the Linux kernel, has announced the release of Linux 6.16-rc3. This release comes with fixes for new features that were introduced during the merge window several weeks ago, and for old features where issues have been detected or improvements need to be made. If you remember last week, Torvalds said that rc2 seemed smaller than usual, putting it down to people going on vacation. He said this week’s rc3 seems to be in the usual ballpark for this time of the cycle, so everything looks “entirely normal.” In terms of changes, this release is “dominated” by wireless networking and GPU driver updates, however, Torvalds doesn’t think that anything really huge stands out this time. While nothing stands out Torvalds urged people to carry on testing and submitting patches. This update saw improvements to the core system and architecture. There have been improvements to ARM64 KVM that improve stability and correctness of virtualizations on ARM64. There are also improvements to RISC-V KVM and Trust Domain Extensions (TDX) for Intel which expand and secure virtualization capabilities on those architectures. On the graphics front, there are fixes for the amdgpu and amdkfd drivers that fix job handling, engine resets, display corruption, and power management features. The driver used for Qualcomm’s Adreno GPUs has been updated to improve fault handling, display timing, and driver binding. The open-source Nouveau (Nvidia) driver has been updated with fixes for GSP message queue references, potential integer overflows, buffer size adjustments, and a use-after-free bug. Finally, the Intel i915 driver has been updated to address early wedge issues, memory initializations, and build errors. There are also improvements to Wi-Fi devices (ath12k and iwlwifi), sound (ALSA), power management on AMD, and file system improvements (OverlayFS, EROFS, XFS, NFS, SunRPC). Linux 6.16 is due for release at the end of July and will then be picked up by Linux distributions, which will be the first interaction most end users have with the new features in this update. The main benefit of a newer kernel is that Linux will work on newer hardware, so if you’ve had issues with Linux, be sure to try it periodically in case your hardware is now supported.
    • Technically, it should be account-bound after activating it
    • Follow this video, and a new build will feel a lot faster. https://www.youtube.com/watch?...WLAytRBid7Qryv3&index=1
  • Recent Achievements

    • Week One Done
      urbanmopdubai1 earned a badge
      Week One Done
    • One Month Later
      Jim Dugan earned a badge
      One Month Later
    • First Post
      Johnny Mrkvička earned a badge
      First Post
    • Week One Done
      viraltui earned a badge
      Week One Done
    • One Month Later
      serfegyed earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      645
    2. 2
      Michael Scrip
      226
    3. 3
      ATLien_0
      219
    4. 4
      Steven P.
      150
    5. 5
      Xenon
      146
  • Tell a friend

    Love Neowin? Tell a friend!