More default parameters in C API

[alexanderwhatley]

Hi, I think it would be great if the some of the functions in the C API had more default parameters (that the users do not have to specify), as well as serializing some additional data. For example:

1. Keep track of the types of the buffers, whether they are of type float*, int*, char**. This would be especially helpful for writing interfaces in dynamically typed languages such as Python and R.
2. Keep track of the largest buffer sizes for each of the buffers. By doing so, the buffer_size parameter in read and write operations could automatically be set to these values.
3. Keep track of the largest buffer size for each individual cell for variable-sized cells. This could be passed in as default for the value parameter in tiledb_array_iterator_get_value.

[stavrospapadopoulos]

Hi there,

All these are valid issues. We are currently building a Python interface (it will be very similar to NumPy, SciPy and SciDB-Py), so probably all these issues will be resolved. Let's revisit this once we publish the Python interface.

Thanks!

[alexanderwhatley]

I see. Is your development branch public on github yet?

On Wed, Jul 20, 2016 at 8:23 AM, Stavros Papadopoulos <
[email protected]> wrote:

Hi there,

All these are valid issues. We are currently building a Python interface
(it will be very similar to NumPy, SciPy and SciDB-Py), so probably all
these issues will be resolved. Let's revisit this once we publish the
Python interface.

Thanks!

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#40 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANiP1kOKr6SvbCGJTBoYxhgbK8Nv_rn9ks5qXj1ZgaJpZM4JNM0y
.

[stavrospapadopoulos]

Hello,

Sorry about the late reply. I have just gotten back from vacation.

This development work is on my local repo. I am still shaping the Python interface. I do not want to publish this yet, as it is undergoing too many changes.

However, I could commit some skeleton work on my local fork, and you could gain access to it. It would be great if you could then share your thoughts about what is good and what to change! I'll try to have this done soon.

Cheers,
Stavros

[alexanderwhatley]

That sounds good thanks.

On Tuesday, August 2, 2016, Stavros Papadopoulos [email protected]
wrote:

Hello,

Sorry about the late reply. I have just gotten back from vacation.

This development work is on my local repo. I am still shaping the Python
interface. I do not want to publish this yet, as it is undergoing too many
changes.

However, I could commit some skeleton work on my local fork, and you could
gain access to it. It would be great if you could then share your thoughts
about what is good and what to change! I'll try to have this done soon.

Cheers,
Stavros

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#40 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANiP1vzizzIdPwsKr8ry9VpOfx34ylJpks5qb2TPgaJpZM4JNM0y
.

[erhanbas]

Hello, any updates on Python interface? thx!

[stavrospapadopoulos]

Hi there. In fact yes, we are starting its more aggressive development now. Please stay tuned, we will try to have it out very soon! :)