the naming convention in our C library program about angka

[yudhastyawan]

for the variable, I prefer vectorstring instead of vectorString. Then, the previous commit follows this type of code.

[yudhastyawan]

I am a fool with this issue. We should care more about this naming convention, especially how people would do in C programming. Let me standardize this naming for our C library code.

Naming Convention

No.	definitions	prefix/suffix	examples
1.	variables - local (trivial)	-	i,n,a,b,... ii,nn,aa,bb,... (if a trivial var name is long, then consider to be a local var)
2.	variables - local (descriptive)	- (camelCase)	variable,variableFoo,...
3.	variables - global	g_	g_variable,g_variableFoo,... (don't use global variabel except for critical purposes)
4.	variables - constant	c_	c_variable,c_variableFoo,...
5.	pointer	p_	p_variable,p_variableFoo,...
6.	array	r_	r_variable,r_variableFoo,...
7.	struct	s_	s_name,s_name_foo,...
8.	union	u_	u_name,u_name_foo,...
9.	enum	e_	e_name,e_name_foo,...
10.	struct (member)	-	variable,r_variable,variableFoo,...
11.	union (member)	mu_	mu_variable,mu_variableFoo,...
12.	enum (member) (except e_bool)	AGX_	AGX_VARIABLE,AGX_VARIABLE_FOO,...
13.	function	agx_	agx_name_function(),...
14.	macro	AGX_	AGX_VARIABLE,AGX_VARIABLE_FOO,...
15.	typedef (struct, union, enum)	Agx (PascalCase)	AgxName, AgxNameFoo...
16.	typedef (data types)	_t	variable_t,p_variable_t, p_variableFoo_t,...

agx_, Agx_, and AGX are used for the Identity of our library code and avoiding conflicting names in C programming.

The Further Idea

agx = the data manipulation
agv = the data visualization
agc = the applied cases (seismology, etc.)
aga = the animation
agtk = gtk+3 support

[yudhastyawan]

For the file name, we can use lowercase with _, such as: agx_matrix.c, agx_vector.h, agx_name_foo.c.

[yudhastyawan]

the name of a function should not use the abbreviation or the difficult name. Keep the function readable.