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

nativeInt (int) is the only native type that is documented #1512

Closed
AlexDaniel opened this issue Sep 3, 2017 · 3 comments
Closed

nativeInt (int) is the only native type that is documented #1512

AlexDaniel opened this issue Sep 3, 2017 · 3 comments
Labels
docs Documentation issue (primary issue type)

Comments

@AlexDaniel
Copy link
Member

This is a continuation of #372.

I think the table we have in nativecall is enough, but maybe not. In fact, I see that types that you can use in nativecall signatures are not identical to what you can use with variables, so I guess I'm missing something.

@AlexDaniel AlexDaniel added the docs Documentation issue (primary issue type) label Sep 3, 2017
@JJ
Copy link
Contributor

JJ commented Apr 7, 2018

What do you think should be done? Document every possible type?

@zoffixznet
Copy link
Contributor

FWIW the CaR grant branch that'll be merged after next release (2018-05-19) adds a "Numerics" language page that does mention native types.

@JJ
Copy link
Contributor

JJ commented May 13, 2018 via email

@JJ JJ removed the JJ TPF Grant label May 14, 2018
JJ added a commit that referenced this issue May 30, 2018
This file actually did not have anything, causing more confusion than
benefit, as indicated by @jnthn in #1534. The native types are right
now described in nativecall, but they will be moved somewhere else, as
per #1512.

Also changes redirection to the new page that includes all these types.
JJ added a commit that referenced this issue May 30, 2018
I have moved the table to this page and split it in two, eliminating
nonspec types. It will clarify what you can use in native call (those
declared with nativesize) and which ones you can't. Refs #1512.
JJ added a commit that referenced this issue May 30, 2018
And the other way round. Refs #1512
JJ added a commit that referenced this issue May 30, 2018
@JJ JJ closed this as completed in 7ffae42 May 30, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Documentation issue (primary issue type)
Projects
None yet
Development

No branches or pull requests

3 participants