This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
notes:discrete:fall2023:projects:dap0 [2023/09/27 21:18] – [Deleting a node within a singly-linked list] walley | notes:discrete:fall2023:projects:dap0 [2023/09/28 01:36] (current) – [sound] jhimmel2 | ||
---|---|---|---|
Line 13: | Line 13: | ||
Note: The remainder you get at each step will become part of the new base number. The new base number is obtained by putting the remainders in reverse order. | Note: The remainder you get at each step will become part of the new base number. The new base number is obtained by putting the remainders in reverse order. | ||
+ | |||
+ | |||
+ | An example of converting the decimal number 29 to binary would look something like this, | ||
+ | |||
+ | ^ Step ^ Operation | ||
+ | | 1 | 29/2 | 14 | 1 | | ||
+ | | 2 | 14/2 | | ||
+ | | 3 | | ||
+ | | 4 | | ||
+ | | 5 | | ||
+ | |||
+ | with the first remainder value becoming the least significant digit. | ||
+ | |||
=====Converting between bases===== | =====Converting between bases===== | ||
Line 21: | Line 34: | ||
In terms of our breakout, in which our brick structures are stored within our singly-linked list. When a brick is destroyed, it's likely that you're simply turning the visible flag to false. Once a brick is invisible, it still exists in memory even if nothing interacts with it. Freeing that brick from memory will improve performance, | In terms of our breakout, in which our brick structures are stored within our singly-linked list. When a brick is destroyed, it's likely that you're simply turning the visible flag to false. Once a brick is invisible, it still exists in memory even if nothing interacts with it. Freeing that brick from memory will improve performance, | ||
+ | |||
+ | In our singly-linked list, we have two pointers: one at the start of the list and one at our current position in the list. Due to the limitations of the structure, we're unable to delete the node we're currently have selected with the current pointer. We're only able to delete the node before or after the one currently selected. In this example, we'll delete the one after. | ||
+ | |||
+ | To start, create a new brick struct pointer. We'll call it '' | ||
+ | |||
+ | In order to make sure our list still stays in one piece after the node deletion, you'll need to assign '' | ||
+ | |||
+ | Afterwards, free the memory allocation of the temp node. Vircon32 has this as a function called '' | ||
====sound==== | ====sound==== | ||
.wav files can be included into your programs to produce sound. | .wav files can be included into your programs to produce sound. | ||
+ | |||
+ | You can include a sound for various reasons. | ||
The first thing you will want to do is to include the .wav file in your Make.sh. To do that nano into your make.sh and add the following: | The first thing you will want to do is to include the .wav file in your Make.sh. To do that nano into your make.sh and add the following: |