C / C++ / MFC

void sortarray(char str[],char *final)
{
	int counter[26] = {0};			// Counter for each of 26 letters, initialised at 0.
	int finallength = 0;			// Length of the final array.
	int i;

	// Count occurences.
	for(i=0;str[i];i++)			// Loop until the terminating zero.
		counter[str[i]-'a']++;		// [str[i]-'a'] is a number 0-25 for the letters a-z.

	// Calculate length of final array.
	for(i=0;i<26;i++){			// Based on number of occurences for each letter.
		if(counter[i])
			finallength += 4;
		if(counter[i] > 9)
			finallength ++;
	}
	
	// Allocate final array.
	final = (char*)malloc(finallength+1);
	final[0] = 0;				// Initialise to empty string for strcatting.

	// Fill the final array.
	char part[6];
	for(i=0;i<26;i++)
		if(counter[i]){
			sprintf(part,"%c %d;",i+'a',counter[i]);
			strcat(final,part);
		}
	final[finallength-1] = 0;		// Remove the last semicolon.

	// Print the final array.
	printf(final);
}

int test = counter[i];
while (test >= 10)
{
   ++finalLength;
   test /= 10;
}

atikot wrote:

can anyone help me come up with more reasonable solution?

// CharCount.c : Defines the entry point for the console application.

#include <string.h>
#include <stdlib.h>
#include <stdio.h>

void CharCount(char str[], char** result)
{
	int i;
	unsigned int count[256];
	if (!strlen(str))
		return;
	if (*result = (char*)malloc(min(strlen(str), 256) * 8)) // Allocate a 'reasonable' output size
	{
		char* out = *result;
		memset(count, 0, sizeof(count));
		for (i = 0; str[i]; i++)
			++count[str[i]];
		for (i = 0; i < 256; i++)
			if (count[i])
				out += sprintf(out, "%c %u;", (char)i, count[i]);
		*--out = '\0';
	}
}

int main()
{
	char* out = NULL; 
	CharCount("abbacdeefg", &out);
	if (out)
		printf("%s\n", out);
	free(out);
}

Mark Salsbery wrote:

The key is per-handle, not per device.

csrss wrote:

...my server prototype is running on localhost and not event close to be loaded so every call to wsasend / wsarecv completes right away without waiting and i am manually posting completion packets with PostQueuedCompletionStatus to simulate expected behavior, where key param is my struct of course, and IO operation is updated before packet is actually posted. So on the other end, i am parsing IO operations correctly. But, i am thinking now, if wsarecv will block and completion packet will arrive some time later

Mark Salsbery
Microsoft MVP - Visual C++

csrss wrote:

By "blocking" i meant a situation where you "post" wsarecv / wsasend and it returns error_io_pending and then awaits for completion packet in worker thread :P

Mark Salsbery
Microsoft MVP - Visual C++

IoObj - Base class for I/O
  IoHnd - IFS handle based
    File - OS file access
    NetSocket - Network socket
      NetIpClnt/NetIpSvc, NetTCP*, NetUdp*, NetIrda*, NetBth*, ...
        NetFPT*, NetNNTP*, ...

WSAOVERLAPPED
  IoOL - Base overlapped; adds flags, timestamps, type, control, buffer
    NetIoOLAddr - specialied for sendto/recfrom, contains remote address
    NetIoOLAccept - specialized for handling AcceptEx

IoCP - I/O completion port