PInvoke & Packet Tables

Open
  • Is something wrong?
#99 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp
Domain
api

Research direction

Start by reviewing the existing P/Invoke declarations for the HDF5 C API and the high-level Packet Table interface. Determine which Packet Table operations are missing and whether the project has a planned extension. Done means the required high-level declarations are supported or the issue is resolved with a documented workaround.

Written by the indexing model from the issue text.

Description

enhancement question

“A complete set of Platform Invoke (P/Invoke) declarations for the core HDF5 C-API is supported”

But I can find no evidence of a packet table interface. I suppose since the Packet Table is part of the High Level interface, it doesn’t count as “core”. Is there a workaround or pending update that would extend the interface to include the high-level stuff? I use Packet Tables almost exclusively for datasets, and having to roll my own seems like a problem. I’d likely stick with my old HDF5DotNet implementation.

Scott

Dominant language
C#
Stars
87
Forks
32
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from HDFGroup/HDF.PInvoke

All issues in HDFGroup/HDF.PInvoke

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.