|
As already suggested, that's the famous bubble sort (the most intuitive one: lower elements comes up).
You may notice that
for (i = 0; i < length; i++)
could be replaced by
for (i = 0; i < length-1; i++)
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
[My articles]
|
|
|
|
|
So whenever a comparison like that is required, a bubble function is used, right?
|
|
|
|
|
There's no bubble function, actually. From Wikipedia[^] : "The algorithm gets its name from the way smaller elements 'bubble' to the top of the list".
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
[My articles]
|
|
|
|
|
Babylon Lion wrote: whenever a comparison like that is required, a bubble function is used, right?
The bubble sort is not the most efficient method of sorting data as there is a lot of swapping going on. In a short list (array) it works fine and is quicker and easier to code. With a shorter list there really isn't too much loss of efficiency.
This site provides a good visual demonstration of the different types of sorts http://www.sorting-algorithms.com/[^]
As Superman states use the std::sort function if you can, although learning sort algorithms can be useful.
Good luck!
It was broke, so I fixed it.
|
|
|
|
|
QuickSort is infinitely faster than a bubble sort. I use it exclusively. It recursively breaks the list up into smaller and smaller pieces. The resulting time-to-sort relative to the length of the list is linear instead of exponential.
Found this from Googling QUICKSORT.
There are many other sources of info out there.
void swap(int *x,int *y)
{
int temp;
temp = *x;
*x = *y;
*y = temp;
}
int choose_pivot(int i,int j )
{
return((i+j) /2);
}
void quicksort(int list[],int m,int n)
{
int key,i,j,k;
if( m < n)
{
k = choose_pivot(m,n);
swap(&list[m],&list[k]);
key = list[m];
i = m+1;
j = n;
while(i <= j)
{
while((i <= n) && (list[i] <= key))
i++;
while((j >= m) && (list[j] > key))
j--;
if( i < j)
swap(&list[i],&list[j]);
}
swap(&list[m],&list[j]);
quicksort(list,m,j-1);
quicksort(list,j+1,n);
}
}
|
|
|
|
|
danataylor wrote: QuickSort is infinitely faster than a bubble sort
In general it is; but in its worse case, it's as bad as other sorts.
Watched code never compiles.
|
|
|
|
|
QuickSort isn't "infinitely" faster than a bubble sort. Its efficiency depends on the choice of pivot, and its performance can be sensitive to the initial order (as explained in that article). For small arrays a bubble sort can be faster!
It's usually better to use a built-in sort because that will have had time spent on it to reduce such problems.
|
|
|
|
|
I would recommend the use of the functions from the standard library like qsort or qsort_s.
|
|
|
|
|
«_Superman_» wrote: I would recommend the use of the functions from the standard library like qsort or qsort_s.
agreed! save time
"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow
Never mind - my own stupidity is the source of every "problem" - Mixture
cheers,
Alok Gupta
VC Forum Q&A :- I/ IV
Support CRY- Child Relief and You
|
|
|
|
|
Interesting sort functions. The first function can be associated to a "bubble sort" except nothing is "bubbling up" in the list array. The inner loop is only storing the index of the smallest value. Then at the end of the second loop (bottom of the first loop), the values are swapped. This is more efficient than a bubble sort because we are not swapping the items in the array (excessive memory access) every time we determine that (list[j] < list[min]). The swap is done n times rather than (n * n) times.
The second sort is sorting an array of indexes based on the percentage change. The original list array is untouched. It is used only for reference. The final result is the indexByGain array. This should be returned. But, it is not and so is lost. For the reporting, the programmer would need to run through the indexByGain to print out the report as:
for (int k = 0; k < length; k++)
printf("%f\n", list[indexByGain[k]].getPercentChange());
assuming that getPercentChange() returns a double or float. Sorry, my C coding is a bit rusty.
|
|
|
|
|
Array.Sort and ArrayList.Sort are both Quick Sorts. Can you create either of these with your data and use them?
"Coding for fun and profit ... mostly fun"
|
|
|
|
|
The first one (sort()), scans the list to find the smallest item (it assumes that elemType has operator<() defined, which we presume is bases on it's ticker symbol string). It then swaps that items with the item in list[0]. Next it scans for the smallest between list[1] and the end, and swaps that with list[1], and onward, swapping the smallest among list[2] & the end with list[2]. I believe this actually makes it an insertion sort, which is slightly faster that a bubble sort (and generally considered the best for small lists)
The second sort (sortByGain()) doesn't want to change the order of the items in list (which presumably have just been sorted by sort()), so it creates a array of indexes into list, so that after both functions are called list[0] is the first stock alphabetically, while list[indexByGain[0]] is the stock with the highest gain.
sortByGain() does a proper (slow) Bubble sort, potenially swapping after every compare, moving the desired item (which is the smallest in the first sort and the largest in the second) one position closer to it's final location each time.
Truth,
James
|
|
|
|
|
Hello,
Im using a bunch of owner-drawn button in an MFC application Im updating. Im loking for an easy way to keep the buttons down when selected and implimenting ToolTip. Ive looked everywhere I can think of and cant find a solution.
Thanks in advanced
Derrek
|
|
|
|
|
|
You may change the button style from BS_PUSHBUTTON to BS_CHECKBOX|BS_PUSHLIKE. The the states should automatically be OK, also for owner drawn buttons.
To change the style, you may use the overloaded method PreSubclassWindow with the help of ModifyStyle(BS_PUSHBUTTON,BS_CHECKBOX|BS_PUSHLIKE);
|
|
|
|
|
Not sure if this is the correct area of the forum for this but here goes:
I have a solution which has 2 exe apps within it (both console apps).
Application (1) kicks of an instance of application (2) using the windows API function CreateProcess().
My question is how do I go about debugging application (2)? - using the standard attach to process option doesn't seem to be working and visual studio never enables my breakpoints.
|
|
|
|
|
You could start a next instance of the VS
and then - select the menu item "Tools->Attach to process" there
They sought it with thimbles, they sought it with care;
They pursued it with forks and hope;
They threatened its life with a railway-share;
They charmed it with smiles and soap.
|
|
|
|
|
|
Hi,
Does anyone know of a free app to list DLL exports? I have tried DLL Export Viewer v1.41 by Nir Sofer but my virus checker prevents me running it.
|
|
|
|
|
Try it[^]
They sought it with thimbles, they sought it with care;
They pursued it with forks and hope;
They threatened its life with a railway-share;
They charmed it with smiles and soap.
|
|
|
|
|
Thanks, that works a treat. I remember this now from a long time ago - it just got better!
 
|
|
|
|
|
|
and then there is DUMPBIN, a Visual Studio command-line utility.
|
|
|
|
|
Hi Guys,
Need help in the current task..
I was trying to put a CMFCToolBar inside the CFormView and i thought will have no problems and used the code bellow. Now this form view is to be kept a Dockable pane. But while doing this i got few problems. To put the toolbar in the FormView, i did this..
The TOOLBAR in the RC File is like this..
IDR_TOOLBAR1 TOOLBAR 16, 16
BEGIN
BUTTON IDC_BTN_1
BUTTON IDC_BTN_2
BUTTON IDC_BTN_3
END
The InitialUpdate of the FormView Derived class is like this: -
<span style="COLOR: blue">void</span> CMyFormView::OnInitialUpdate()
{
CFormView::OnInitialUpdate();
CWnd *pWnd = NULL;
CRect rcPos;
<span style="COLOR: blue">if</span>(!m_wndToolView.Create(<span style="COLOR: blue">this</span>, AFX_DEFAULT_TOOLBAR_STYLE, IDR_TOOLBAR1))
{
TRACE0(<span style="COLOR: #a31515">"Failed to Create Dialog Toolbar\n"</span>);
}
m_wndToolView.LoadToolBar(IDR_TOOLBAR1, 0, 0, TRUE <span style="COLOR: green"></span>);
m_wndToolView.CleanUpLockedImages();
m_wndToolView.LoadBitmap(IDR_TOOLBAR1, 0, 0, TRUE <span style="COLOR: green"></span>);
m_wndToolView.SetPaneStyle(m_wndToolView.GetPaneStyle() | CBRS_TOOLTIPS | CBRS_FLYBY | WS_CHILD | WS_TABSTOP);
m_wndToolView.SetPaneStyle(m_wndToolView.GetPaneStyle() & ~(CBRS_GRIPPER | CBRS_SIZE_DYNAMIC | CBRS_BORDER_TOP | CBRS_BORDER_BOTTOM | CBRS_BORDER_LEFT | CBRS_BORDER_RIGHT));
m_wndToolView.SetOwner(<span style="COLOR: blue">this</span>);
CSize szToolBar = m_wndToolView.CalcFixedLayout( FALSE, TRUE ); <span style="COLOR: green">
}
Now a few problems i am getting are: -
1. The Toolbar images are not coming proper
2. The Update of the Toolbar items is not coming.
HARSH
Programmers are in a race with the Universe to create bigger and better idiot-proof programs, while the Universe is trying to create bigger and better idiots. So far the Universe is winning.
|
|
|
|
|
May be also done as following
int CDiaFrame::OnCreate(LPCREATESTRUCT lpCreateStruct)
{
if (CFrameWnd::OnCreate(lpCreateStruct) == -1)
return -1;
ModifyStyle(0, WS_CLIPCHILDREN);
ModifyStyleEx(WS_EX_CLIENTEDGE, 0);
m_cToolBar.Create(this, WS_CHILD | WS_VISIBLE | CBRS_TOP, 1);
m_cToolBar.SetPaneStyle(m_cToolBar.GetPaneStyle() | CBRS_TOOLTIPS | CBRS_FLYBY);
m_cToolBar.SetPaneStyle(m_cToolBar.GetPaneStyle() & ~(CBRS_GRIPPER | CBRS_SIZE_DYNAMIC | CBRS_BORDER_TOP | CBRS_BORDER_BOTTOM | CBRS_BORDER_LEFT | CBRS_BORDER_RIGHT));
m_cToolBar.LoadToolBar(IDR_DIATOOLBAR, 0, 0, TRUE);
return 0;
}
void CDiaFrame::OnSize(UINT nType, int cx, int cy)
{
CFrameWnd::OnSize(nType, cx, cy);
static CSize sizeToolBar(m_cToolBar.CalcFixedLayout(TRUE, TRUE));
CRect crClient;
GetClientRect(crClient);
crClient.bottom = sizeToolBar.cy;
m_cToolBar.MoveWindow(crClient);
}
And then - create/size this frame in a docable pane.
Of course you have to define the frame's reactions/updates for all commands from your bar as well
They sought it with thimbles, they sought it with care;
They pursued it with forks and hope;
They threatened its life with a railway-share;
They charmed it with smiles and soap.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
