zString | A permissive licensed string manipulation library for C

This can be easily done using the pandas module. If you are OK to use pandas module, you could read your csv as follows.

Casting will not solve the issue and perhaps you have illustrated why casting is bad.

You need a function like something like this,

The importc pragma is used to import a proc or variable from C. However, you are writing importc: "name New", and name New is not a valid identifier in C because it has a space in it. You would need to try to concatenate the symbolic name of the variable you are passing into the template with that additional string sufix.

I don't know how you can do that in a template, though. Maybe you could pass a string as parameter and then use the & operator to concatenate it with the suffix for importc.

If I understand your intention correctly, you want to append the xdata,ydata,zdata from each row in the file to the X, Y, Z lists and in the end plot (scatter) these lists. However, your code doesn't append to the lists inside the loop, so you end up applying scatter just on the last xdata, ydata, zdata.

if you want that some function containing single jmp instruction to some address - you need declare it with __declspec(dllimport) (this is Microsoft Specific and work only for CL compiler but think another compilers have equvalent syntax). say for example

This snippet goes at the bottom of a function (which can't inline, and must be compiled with ebp as a frame pointer, and no other registers that need restoring). It looks quite brittle, or else it's only useful in cases where you didn't need inline asm at all.

Instead of returning, it jumps to uAddr, which is equivalent to making a tailcall.

There aren't intrinsics for arbitrary jumps or manipulation of the stack. If you need that, you're out of luck. It doesn't make sense to ask about this snippet by itself, only with enough context to see how it's being used. i.e. is it important which return address is on the stack, or is it ok for it to compile to call/ret instead of jmp to that address? (See the first version of this answer for a simple example of using it as a function pointer.)

From your update, your use-cases are just a very clunky way to make wrappers for absolute function pointers.

We can instead define static const function pointers of the right types, so no wrapper is needed and the compiler can call directly from wherever you use these. static const is how we let the compile know it can fully inline the function pointers, and doesn't need to store them anywhere as data if it doesn't want to, just like normal static const int xyz = 2;