IXP_WRITE(3)

✨ IXP_WRITE(3) — the write-your-data-to-a-file girlies ✨

okay so bestie, this is a page from the Library Functions Manual — yes, the IXP_WRITE(3) one, the one you've been looking for 💅 come sit with me, this one's actually so straightforward it's giving "ate and left no crumbs".

🌸 NAME 🌸

ixp_write, ixp_pwrite — literally the two functions that put your bytes into the file, no cap 🫶

🦋 SYNOPSIS 🦋

#include <ixp.h>

long ixp_write(IxpCFid *fid, const void *buf, long count);

long ixp_pwrite(IxpCFid *fid, const void *buf, long count, int64_t offset);

like, look at them. two little icons. both long, both taking your fid, your buf, your count — and one of them is the extra-special version that also grabs an offset 💖

🎀 PARAMETERS 🎀

• buf — the buffer holding the contents to store. this is your actual data, your moment, your main character payload 🌈
• count — the number of bytes to store. how much of the vibe you're committing to, fr fr.
• offset — the offset at which to write the data. only ixp_pwrite gets this one, she's the fancy one 👑

💜 DESCRIPTION 💜

so ixp_write and ixp_pwrite each write count bytes of data stored in buf to the file pointed to by fid. iconic. both of them. same energy.

the difference is where the bytes land, and it's honestly the whole plot:

• ixp_write writes its data at its stored offset, and increments it by count. so she's the "keep going where I left off" girl — she bookmarks herself, moving forward by exactly count every time 🔥
• ixp_pwrite writes its data a offset and does not alter fid's stored offset. so she hits exactly the spot you tell her to, and then she leaves the bookmark completely untouched. respectful. considerate. so not messy 🙈

like, one of them remembers where she was, one of them doesn't touch the bookmark at all. that's it, that's the whole tea ☕

⭐ RETURN VALUE ⭐

these functions return the number of bytes actually written. so you get a number back — check it, bestie, don't just vibe-check it and move on.

⚠️ any value less than count must be considered a failure. must, okay?? if it's less than count, something went wrong and you need to handle it, no cap, i'm not playing around on this one 💀

🧚 SEE ALSO 🧚

• ixp_mount(3)
• ixp_open(3)
• ixp_read(3)

(been there, read that, the whole little friend group 🫶)

and that's the page, bestie!! mwah 💋 this was brought to you by the libixp Manual, dated 2012 Dec, and the header IXP_WRITE(3) you saw at the very top of this whole thing — that's her name, and she ate. periodt. 🎀✨💖