Practical design patterns in C
Table of Contents generated with DocToc
Practical Design Patterns in C
This will be a repository of
======================================================
private protected public static pure
-------------------+--------+-------+--------+-----+--
constructor + + +
destructor
virtual +
methods
virtual + +
routine + + +
variables
member - + +
=================================================
+ have implemented
- can implemented with the "handle/body" idiom, but ...
Make a pattern
--------------
$ cd auto-gen
$ make
$ make runall
$ make clean_all
Auto Generate class
-------------------
$ cd tools
$ python gencode.py --file json/prototype.json > log <<< the generated code in dir ./tools/code/c/prototype
The oop come from myobj.h:
struct shape_rectangle *rect;
rect = malloc(sizeof(*rect));
if (!rect) return -1;
shape_rectangle_init(rect);
shape_draw(&rect->shape);
shape_free(&rect->shape);
struct shape_ops;
struct shape {
struct shape_ops *ops;
struct color * _color;
};
struct shape_ops {
void (*_destructor)(struct shape *);
void (*free)(struct shape *);
void (*draw)(struct shape *);
struct shape_ops *__super;
};
void shape_init(struct shape *);
struct shape_rectangle *rect;
shape_rectangle_init(rect);
shape_draw(&rect->shape);
shape_free(&rect->shape);
struct shape_rectangle {
struct shape shape;
};
void shape_rectangle_init(struct shape_rectangle *);
struct shape_rectangle *rect;
struct shape_circle *circle;
shape_draw(&rect->shape);
shape_draw(&circle->shape);
// file: OOC.h
struct Class {
size_t size;
void *(* ctor) (void *self, va_list *app);
};
void *new(const void *_class, ...) {
const struct Class *class = _class; // assign the address of `struct String` class
void *p = calloc(1, class->size); // allocate the sizeof(struct String);
assert(p);
*(const struct Class **)p = class; // Force the conversion of p and set the argument `class` as the value of this pointer.
if(class->ctor) {
va_list ap;
va_start(ap, _class);
p = class->ctor(p, &ap); // Now what is `p` here, a `struct String` or `struct Class`.
// and if it is `struct Class` then how it convert to `struct String` in `String_ctor` function
// given below.
va_end(ap);
}
return p;
}
// file: mystring.h
#include "OOC.h"
struct String {
const void *class; // must be first
char *text;
};
static void *String_ctor(void *_self, va_list *app) {
struct String *self = _self;
const char *text = va_arg(*app, const char *);
self->text = malloc(strlen(text) + 1);
assert(self->text);
strcpy(self->text, text);
return self;
}
// Initialization
static const struct Class _String = {
sizeof(struct String),
String_ctor
};
const void *String = &_String;
// file: main.c
#include "mystring.h"
int main(void)
{
void *a = new(String, "some text");
}
The repository contains a folder by each design pattern.
oop: http://www.codeproject.com/Articles/22769/Introduction-to-Object-Oriented-Programming-Concep http://www.tutorialspoint.com/cplusplus/cpp_object_oriented.htm http://oopsconcepts.blogspot.ca/
ops -> vtable
t_ops -> half class level vtable
caps -> DI - callback (construct)
cbs -> DI - client/request callback (argument)
The SOLID principles of object-oriented programming
framework-lib cooperate with client:
All constructive comments are welcome. Please feel free to fork and extend existing or add your own examples and send a pull request with your changes!
The MIT License (MIT)
Copyright (c) 2014 Wilson Huawen Yu
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
PyNSource - UML tool for Python
Design Patterns Explained Simply
.NET Design Patterns
Software design pattern
Computer Science Design Patterns