Description of Change

• Add cmake based structure
• Include documentation building
• Add GitHub Actions using cmake to check code compilation on linux (ubuntu), Mac OS and Windows (using MS Visual C/C++ compiler)
• Add GitHub action to auto-generate documentation and push to repo's respective GitHub Pages -> this will create the website https://thealgorithms.github.io/C similar to https://kvedala.github.io/C
• add documentations to various source codes including mathematical formulations where possible
• fix code formatting issues with existing files
• fix source codes so they compile on all operating systems
• github actions workflow improved by
  • adding auto format code and file name
  • stage-by-stage actions for efficient checks

This documentation approach will also enable other contributors to add documentation in their respective languages or use google translate to do so.

Checklist

• [x] Added description of change
• [x] Added file name normalization - all small letters and no spaces
• [x] Added tests and example, test must pass - wherever possible
• [x] Relevant documentation/comments is changed or added
• [x] PR title follows semantic commit guidelines
• [x] Search previous suggestions before making a new one, as yours may be a duplicate.
• [x] Sort by alphabetical order
• [x] I acknowledge that all my contributions will be made under the project's license.

Note

Before merging, the parent repository branch structure would need to be improved (Adding images branch, adding gh-pages branch). Unless existing maintainers are up for the challenge, I,d like to volunteer to maintain the structure of the repo and the documentation of the same. It’d allow us to have graphs and files for a much better documentation.

I create leetcode directory. You can contribute solution for Leetcode algorithm by C language. Good practice coding :) Please put some comment for explanation. It helps other people understand your algorithm better

Description of Change

absolute value

References

Checklist

• [x] Added description of change
• [x] Added file name matches File name guidelines
• [x] Added tests and example, test must pass
• [x] Relevant documentation/comments is changed or added
• [x] PR title follows semantic commit guidelines
• [x] Search previous suggestions before making a new one, as yours may be a duplicate.
• [x] I acknowledge that all my contributions will be made under the project's license.

Notes:

Hello, i created a new directory named "debugging". In this directory, i have created three new files : malloc_dbg.c, malloc_dbg.h and test.c

The main objective of these files is to know where a memory leak occurred (even on a Windows computer where valgrind doesn't exists and without having to use WSL). The test.c only contains a main function in which we call malloc and calloc and we only free one of the two pointers.

In malloc_dbg.h there are three macros : malloc, calloc and free. There are also the prototypes of the functions malloc_dbg, calloc_dbg, free_dbg and printLeaks.

The malloc_dbg.c file contains the definitions of the above functions and a structure (a doubly linked list which is used to store a pointer returned by malloc/calloc, the number of bytes that have been allocated, the file from where malloc/calloc was called and the line number of this call).

malloc_dbg and calloc_dbg functions both calls atexit() to make sure the leaks will be printed at the end of the execution.

In test.c file, we simply include malloc_dbg.h to be able to use the macros.

When the program exits, it should print if there are memory leaks or no, for example : "Memory Leaks detected.

256 bytes lost address : 0x0x558c8a33e310 in main test.c:23

==================================== SUMMARY : 256 bytes lost in 1 blocks"

This has been tested under Linux and Windows.

Description of Change

A solution for the ZigZag conversion problem.

References

Hacktoberfest issue

ZigZag Conversion problem on leetcode

Checklist

• [x] Added description of change
• [x] Added file name matches File name guidelines
• [x] Added tests and example, test must pass
• [x] Relevant documentation/comments is changed or added
• [x] PR title follows semantic commit guidelines
• [x] Search previous suggestions before making a new one, as yours may be a duplicate.
• [x] I acknowledge that all my contributions will be made under the project's license.

Notes: Solution to the 6-ZigZag conversion problem was missing. Here is (decent) one.

ZigZagConversion-SubmissionDetail-LeetCode.pdf

Description of Change

References

Checklist

• [x] Added description of change
• [x] Added file name matches File name guidelines
• [x] Added tests and example, test must pass
• [x] Relevant documentation/comments is changed or added
• [x] PR title follows semantic commit guidelines
• [x] Search previous suggestions before making a new one, as yours may be a duplicate.
• [x] I acknowledge that all my contributions will be made under the project's license.

Notes:

Detailed description

The code provided in the Array Repository can only be understood by advanced C users. I hereby propose a basic array implementation and performing some basic operations using the same array implementation.

Context

This repository according to its description states that it consists of various Algorithms implementation using C language. But the code mentioned in the repository cannot be used by novice coders or other interested people easily. So I suggest a commonly used method of representing arrays along with its commonly used operations.

Possible implementation

No response

Additional information

No response

Description of Change

Issue: #729 As mentioned in the issue , The piece code listed below throws the program into an loop (from line 247) if an invalid character is entered.

        else
        {
+            int n = check_placex();
-             printf("Invalid move\n");

-            printf("Enter new position : ");
-            scanf("%d", &n1);
+           placex(n);
-            placex(n1);
        }
    }
    else
    {
-        printf("Invalid move \n");
+       int n = check_placex();
-        printf("Enter new position : ");
-        scanf("%d", &n1);
+       placex(n);
-        placex(n1);
    }
}

Fixes / Changes

Added an array [dynamic] at line36 :

+ int *stored_pos = NULL;

line 47:

+  stored_pos = (int*)calloc(9,sizeof(int))

Assignment of the stored_pos array:

line 331, line 308 & line 278

example:

+ stored_pos[e] = 1;

Freed the stored_pos memory

line 75

+ free(stored_pos);

Added a new function called check_places at line237 to line256

int check_placex(){
	char input[50];
	int n1;
	while (1){
		fgets(input,49,stdin);
		if ( strlen(input) > 2 || strlen(input)  == 0){
			fprintf(stderr,"Invalid move, Enter number 1 - 9: ");
			continue;
		}
		if(sscanf(input,"%d",&n1) != 1){
			fprintf(stderr,"Invalid move, Enter number 1 - 9: ");
			continue;
		} 
		if ((stored_pos[n1-1] == 1) || (n1== 0)){
			fprintf(stderr,"Already allocated, Enter number: ");
			continue;
		}
		return n1;
	}
}	

The while-loop in the above above function will ask for an input until it gets a correct output.

1. The first if condition checks whether the input is within the range. (strlen() is used so string.h lib is need)
2. Second if condition checks if the value is integer
3. Third if condition checks if the value (posistion) is already occupied.

References

Checklist

• [x] Added description of change
• [x] Added file name matches File name guidelines
• [x] Added tests and example, test must pass
• [x] Relevant documentation/comments is changed or added
• [x] PR title follows semantic commit guidelines
• [x] Search previous suggestions before making a new one, as yours may be a duplicate.
• [x] I acknowledge that all my contributions will be made under the project's license.

Notes:

Description of Change

Add a solution to project euler problem 107 using Kruskal's algorithm. I've followed the contribution guidelines to the best of my abilities, please lmk of any changes you would like to be made. Thank you for your time!

References

Checklist

• [x] Added description of change
• [x] Added file name matches File name guidelines
• [x] Added tests and example, test must pass
• [x] Relevant documentation/comments is changed or added
• [x] PR title follows semantic commit guidelines
• [x] Search previous suggestions before making a new one, as yours may be a duplicate.
• [x] I acknowledge that all my contributions will be made under the project's license.

Notes:

Description of Change

References

Checklist

• [x] Added description of change
• [x] Added file name matches File name guidelines
• [x] Added tests and example, test must pass
• [x] Relevant documentation/comments is changed or added
• [x] PR title follows semantic commit guidelines
• [x] Search previous suggestions before making a new one, as yours may be a duplicate.
• [x] I acknowledge that all my contributions will be made under the project's license.

Notes:

Implemented K Means Clustering in C The data set used for implementing is ordered pair(x,y) in 2D plane.

Description of Change

References

Checklist

• [x] Added description of change
• [x] Added file name matches File name guidelines
• [x] Added tests and example, test must pass
• [x] Relevant documentation/comments is changed or added
• [x] PR title follows semantic commit guidelines
• [x] Search previous suggestions before making a new one, as yours may be a duplicate.
• [x] I acknowledge that all my contributions will be made under the project's license.

Notes: The Link Checks are always failing I am really unable to understand why If you can refer some resources to learn about it that would be really helpful.

Description of Change

Add a guide for new LeetCode solutions.

References

Checklist

• [x] Added description of change
• [x] Added file name matches File name guidelines
• [ ] Added tests and example, test must pass
• [x] Relevant documentation/comments is changed or added
• [x] PR title follows semantic commit guidelines
• [x] Search previous suggestions before making a new one, as yours may be a duplicate.
• [x] I acknowledge that all my contributions will be made under the project's license.

Notes:

Description of Change

Add a guide for new LeetCode solutions.

References

Checklist

• [x] Added description of change
• [x] Added file name matches File name guidelines
• [ ] Added tests and example, test must pass
• [x] Relevant documentation/comments is changed or added
• [x] PR title follows semantic commit guidelines
• [x] Search previous suggestions before making a new one, as yours may be a duplicate.
• [x] I acknowledge that all my contributions will be made under the project's license.

Notes:

Description of Change

Add a guide for new LeetCode solutions.

References

Checklist

• [x] Added description of change
• [x] Added file name matches File name guidelines
• [ ] Added tests and example, test must pass
• [x] Relevant documentation/comments is changed or added
• [x] PR title follows semantic commit guidelines
• [x] Search previous suggestions before making a new one, as yours may be a duplicate.
• [x] I acknowledge that all my contributions will be made under the project's license.

Notes:

Description of Change

Add a guide for new LeetCode solutions.

References

Checklist

• [x] Added description of change
• [x] Added file name matches File name guidelines
• [ ] Added tests and example, test must pass
• [x] Relevant documentation/comments is changed or added
• [x] PR title follows semantic commit guidelines
• [x] Search previous suggestions before making a new one, as yours may be a duplicate.
• [x] I acknowledge that all my contributions will be made under the project's license.

Notes:

Description of Change

Add the leetcode labeler for leetcode change folder label.

References

Checklist

• [x] Added description of change
• [ ] Added file name matches File name guidelines
• [ ] Added tests and example, test must pass
• [ ] Relevant documentation/comments is changed or added
• [x] PR title follows semantic commit guidelines
• [x] Search previous suggestions before making a new one, as yours may be a duplicate.
• [x] I acknowledge that all my contributions will be made under the project's license.

Notes:

Description of Change

Add a guide for new LeetCode solutions.

References

Checklist

• [x] Added description of change
• [x] Added file name matches File name guidelines
• [ ] Added tests and example, test must pass
• [x] Relevant documentation/comments is changed or added
• [x] PR title follows semantic commit guidelines
• [x] Search previous suggestions before making a new one, as yours may be a duplicate.
• [x] I acknowledge that all my contributions will be made under the project's license.

Notes: