shmuelfine / coop Goto Github PK

We look for an information aboat start using with catch2 , we found in this link (https://github.com/catchorg/Catch2/blob/devel/docs/tutorial.md)
we saw there that we can use catch2 with cmake or without cmake, we chose to do it without cmake
(Is it good? Is there a preference to use cmake?)
We look for a link to download the package of catch2 and we found this link, (https://marketplace.visualstudio.com/items?itemName=JohnnyHendriks.ext01&ssr=false#overview)
we found in stackoverflow instructions to start using with catch2 after the download (https://stackoverflow.com/questions/59645381/best-practices-for-unit-testing-with-catch2-in-visual-studio)
we start act according to the instruction and we had a problem in the third step
#include "path_to_catch2/catch.hpp"
we dont know the path_to_catch2
we found a link that explain how to find a location of installed package , (https://askubuntu.com/questions/423355/how-do-i-check-if-a-package-is-installed-on-my-server)
We tried to do what is written there :
//Show the location where the package is installed. The -S (capital S) stands for "search"
sudo dpkg -S {VSTestAdapterCatch2 }
sudo dpkg -S skype
but we got that errore :
M:> dpkg -S VSTestAdapterCatch2
'dpkg' is not recognized as an internal or external command,
operable program or batch file.
how yoperable program or batch file.
we will be happy to get help
thanks

this code was not touched for two years. so I don't really know what is its state right now. check it out:

1. Make it run and make sure all unit tests pass
2. Then, instead of using google tests, use Catch2
3. How can you get rid of the "Proxy" ?

1. Implement Hash Table class, and based on that make a Dictionary
2. The Set should be based on the Tree (with n*log(n) insertion time)

WSL = Windows subsystem for linux

(GObject)[https://en.wikipedia.org/wiki/GObject] is based on Glib, which is a separate task of someone in your team. so you can collaborate on figuring out things.
Your task is:

1. Read its documentation
2. Download the code and try to build it on Windows (don't get stuck if it doesn't work)
3. Understand how it implements constructors and destructors
4. Understand how it implements inheritance

The OOC library is trying to do something similar to what we want.
Your task is to:

1. Read its documentation
2. Download the code and try to build it on Windows (don't get stuck if it doesn't work)
3. Understand how it implements constructors and destructors
4. Understand how it implements inheritance

MinGW and Cygwin are tools with which you can build on Windows code that was written for Linux.
You need to find a tutorial about them and learn how to use them, for helping others to do so as well.
This task will be graded with success when you'll help your team members to build and debug OOC or Glib libraries in that way. (OOC and Glib are explained in other tasks of this team)

Hi! Could you answer couple of architecture questions?

1. I've seen in "Projects", you reviewed existing frameworks prior to create this one. What features were missed? For, example, if compare with known http://ooc-coding.sourceforge.net/.
2. You have note in readme Since C and C++ are compiled differently, there are parts of the COOP infrastructure that can’t be used form within a C++ project.. What limits does it means? I prefer use cpp when available. What limits should i know about? Are those specific for this framework only?

Add a Mat class to COOP - representing a matrix (=single channel image).
Add all the operations of GrayImage to this class.

I see MSVC project files all the way so I'm a bit afraid. Does COOP MSVC only? If it's not then how to use COOP with GCC? Thanks.

Glib is a base library for object-oriented programming in C which does something similar to what we want.
Your task is to:

1. Read its documentation
2. Download the code and try to build it on Windows (don't get stuck if it doesn't work)
3. Understand how it implements constructors and destructors
4. Understand how it implements inheritance

Currently, the memory management statically pre-allocates a certain amount of "blocks"
Which is not efficient - we might need much less, or much more, and using a hard coded number does not make sense.
you can make a memory management mechanism without it.
try to find out how does the malloc and free functions work in C for inspiration.