326fc888e4
allow string shared body
2012-05-31 19:16:48 +09:00
64fc4ac332
resolve conflict
2012-05-31 15:32:38 +09:00
0e5958d404
rename ruby_digitmap to mrb_digitmap
2012-05-30 21:19:04 +09:00
ad9e841c53
made mrb_get_args() better (optinal args, type checks); close #173 #176
2012-05-24 01:09:36 +09:00
1eb02552ea
remove unused prototype from hash.h
2012-05-22 18:51:22 +09:00
c9930d1c32
remove unused MT code from hash.h
2012-05-22 18:49:30 +09:00
9e336b00e5
More C++ compilability work: mrb_obj_alloc void* conversions
...
One of the biggest set of changes needed to make C++ compile, is that you
can't autoconvert "void*" to a different pointer type without a cast (you
can of course, convert pointers *to* "void*"!)
For the first part, convert the users of "mrb_obj_alloc". Since it has
to return something, make it RBasic* (that's what mrb_obj_alloc() is
operating on anyway). This way, even in C you'll get a warning if you
don't cast it.
For places where there are a lot of similar calls to mrb_obj_alloc(),
this can be easily hidden through a macro. I did this in string.c:
#define mrb_obj_alloc_string(mrb) ((struct RString *) mrb_obj_alloc((mrb), MRB_TT_STRING, (mrb)->string_class))
I also updated the mrb_object() macro to also return a RBasic* -- my
previous commit changed that from "void*" -> "RObject*", but I figure
it should be consistent with mrb_obj_alloc()
2012-05-20 09:43:14 -07:00
3471e2b134
C++ compilability - don't define types inside others
...
The following is legal code in both C and C++:
struct foo {
struct bar { int a } x;
int y;
};
...however in C++ it defines a type called "foo::bar" instead of "bar".
Just avoid this construct altogether
2012-05-19 22:40:57 -07:00
aeca23166b
remove dependency to node.h and pool.h
2012-05-19 15:52:47 +09:00
685b4d1c84
fixed a typo
2012-05-18 13:32:47 +09:00
219162117a
move compile.h to mruby/compile.h
2012-05-18 12:54:23 +09:00
bbf7b0ceba
add extern "C" guards
2012-05-18 12:45:09 +09:00
a4d3579e31
add extern "C" guards; close #126
2012-05-18 02:02:49 +09:00
470da1eda0
redefine POST/NEG FIXABLE using INT_MIN/MAX
2012-05-17 09:32:23 +09:00
22bd603a7e
move declaration in the middle
2012-05-09 10:59:05 +09:00
f4cf8ea423
partial VC support
2012-05-09 08:49:38 +09:00
d0e63a3a03
RMatch.src should not be mrb_value
2012-05-07 17:31:07 +09:00
b0e94d8c14
Time class available; based on code from @beoran; sorry for jumbo patch
2012-05-06 00:52:22 +09:00
e0460c1157
hash refactored
2012-05-05 08:55:58 +09:00
c9a51c43bc
use int8_t for tt
2012-05-05 07:59:15 +09:00
eac8e4a303
move mrb_obj_is_instance_of from range.c to kernel.c
2012-05-05 00:21:23 +09:00
e806f55e69
move mrb_str_new prototype to mruby.h
2012-05-04 22:39:21 +09:00
4fd260489e
remove ruby_strdup() prototype
2012-05-01 18:17:58 +09:00
4ec6d41f16
rm whitespace
2012-04-30 14:29:19 -07:00
2b6be16308
Merge pull request #61 from pbhogan/fix-warnings
...
Fix various warnings
2012-04-27 08:56:39 -07:00
32db0e5d8c
struct RString member should not be mrb_value
2012-04-28 00:32:34 +09:00
f9647592ef
Remove unused variable in khash
...
Signed-off-by: Patrick Hogan <pbhogan@gmail.com >
2012-04-26 08:36:32 -05:00
4b8515184d
mrb_read_irep should take const char *
...
Signed-off-by: Patrick Hogan <pbhogan@gmail.com >
2012-04-26 08:36:32 -05:00
a408ba2dd6
Remove unused ret argument from kh_put.
...
It doesn't appear to serve any purpose and allows removing warning about various unused variables littered around.
Signed-off-by: Patrick Hogan <pbhogan@gmail.com >
2012-04-26 08:36:32 -05:00
7b3d628c86
use mrb_float instead of double
2012-04-26 11:13:45 +09:00
8b367098ac
move header files {irep,dump,cdump,ritehash}.h to /include/mruby
2012-04-24 17:41:28 +09:00
2970b6aadb
change type of RString.size from size_t to long
2012-04-24 16:03:42 +09:00
2fc1b8af2d
mv variable.h to mruby/variable.h
2012-04-24 15:59:50 +09:00
a5c0d2a996
remove st_hash_type comment
2012-04-24 11:00:06 +09:00
835443614d
add file header
2012-04-23 11:46:16 +09:00
d1144220cb
move src/mdata.h to include/mruby/data.h
2012-04-20 17:18:30 +09:00
2161737c2d
MRUBY_OBJECT_HEADER is always used with `;', but, in the definition of a struct, you cannot include any statement except declarations, even if the statement is void statement.
2012-04-20 15:35:57 +09:00
e0d6430f63
add mruby sources
2012-04-20 09:39:03 +09:00
Yukihiro Matsumoto