- User Since
- Mar 25 2014, 7:11 AM (264 w, 1 d)
Tue, Apr 16
Mon, Apr 15
Since @segfaultxavi is the one that suggested this rule.
I'm confident he is OK with this push :D
Fri, Apr 12
This will require some changes in the way that our wrappers handle their lifetime.
In case a Dispose happens on an object and it still has references in C, it will need to resurrect itself if it holds any registered delegates or if its C# state is important.
Thu, Apr 11
I tested it, everything seems to be correct now.
But wouldn't it be easier to pass prop.klass/func.klass directly to generate_all_tag_examples than adding a new field to class_context?
Wed, Apr 10
Everything looks fine IMHO.
Everything seems OK to me now.
Very good. Just a note:
Tue, Apr 9
Fri, Apr 5
rework some useless code comments
fix previous update submitting to much code
rebase and adds D8550 as a dependency
Thu, Apr 4
Just a comment:
Mon, Apr 1
Thu, Mar 28
I prefer no namespace indentation in any language whatsoever.
I really hope that no C# style analysis tool enforces it.
Tue, Mar 26
@lauromoura 's fix and rebase
Sadly, it is not =/
We need access to those structs in any object that uses them.
Mon, Mar 25
- eolian_csharp: add indentation context
Thu, Mar 21
Wed, Mar 20
Needs rebasing. test_conflicting_events doesn't exist on master anymore and creates a conflict.
@cedric I solved the concurrency problem using ecore_main_loop_thread_safe_call_async.
Eo error logs disappeared, but now the test prints a big list like this at the end of execution:
EINA ERROR: 'Invalid argument' on unlock 0x7fc693ffe980 EINA ERROR: 'Invalid argument' on lock 0x7fc693ffe980 EINA ERROR: 'Invalid argument' on unlock 0x7fc693ffe980 EINA ERROR: 'Invalid argument' on lock 0x7fc693ffe980 EINA ERROR: 'Invalid argument' on unlock 0x7fc693ffe980 EINA ERROR: 'Invalid argument' on lock 0x7fc693ffe980
Could you give it a look and check whether I am using it incorrectly or it is a problem with eina_thread?
Mar 15 2019
Mar 14 2019
Pretty please with a cherry on top!