Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[MotionTwin] NativeArray::memcmp issue #49

Closed
kiroukou opened this issue Apr 8, 2014 · 2 comments
Closed

[MotionTwin] NativeArray::memcmp issue #49

kiroukou opened this issue Apr 8, 2014 · 2 comments

Comments

@kiroukou
Copy link

kiroukou commented Apr 8, 2014

Hi,

I'm experimenting the following error.
I saw a very recent change about that (yesterday), any idea of what is going on ?

Error: ./src/cpp/NativeArray.cpp: In member function 'virtual Dynamic cpp::NativeArray_obj::__Field(const String&, bool)':
./src/cpp/NativeArray.cpp:112: error: no matching function for call to 'cpp::NativeArray_obj::memcmp(const HX_CHAR* const&, const char [5], unsigned int)'

Thanks
Thomas

@hughsando
Copy link
Member

I have been testing with "using cpp.NativeArray", but not "import
cpp.NativeArray". I suspect that function might need to be "extern".

On Tue, Apr 8, 2014 at 7:14 PM, kiroukou notifications@github.com wrote:

Hi,

I'm experimenting the following error.
I saw a very recent change about that (yesterday), any idea of what is
going on ?

Error: ./src/cpp/NativeArray.cpp: In member function 'virtual Dynamic
cpp::NativeArray_obj::__Field(const String&, bool)':
./src/cpp/NativeArray.cpp:112: error: no matching function for call to
'cpp::NativeArray_obj::memcmp(const HX_CHAR* const&, const char [5],
unsigned int)'

Thanks
Thomas

Reply to this email directly or view it on GitHubhttps://github.com//issues/49
.

@delahee
Copy link
Contributor

delahee commented Apr 10, 2014

good for close.

@Simn Simn closed this as completed Apr 10, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants