Search:

I think I found my solution:


typedef struct _NEW_PAWS
{
NEW_PAWBUF buff;
pawhhs args;
va_list *va;
} NEW_PAWS;

To keep the context short & sweet:


typedef struct _NEW_PAWS
{
NEW_PAWBUF buff;
pawhhs args;
va_list va;
} NEW_PAWS;

Found the cause, was feeding the wrong value into a termination function, just uploaded the fix if anyone's curios enough to look

I'll start with the links:

In main():
src/trypaw/trypaw.c * d2939bb458a21a01b93a92907b8b21c5330e857f * Lee Shallis / Dragonbuilder * GitLab

Bottom of the stack:
src/libpaw/global/gcbuff.c *...

Never mind, just found what I was looking for:

lseek64(3) - Linux man page

Coulda sworn that was supposed to return long long, whatever at least I have it now

Implementing the offset getting/setting part of my io api and remembered that off64_t/off_t were more useful for providing consistent support for large files, problem is my attempts to find the...

Another way to put it is this, to the cpu the division is done roughly the same as you would normal numbers, only it's using just 0 & 1, so when it reaches bit -1 it quits because that cannot be...

Never mind, it was because I was incrementing end in the wrong place at the top of the 1st loop, adding braces to the continue statement below it and shifting the increment to there and putting "end...

Getting a segfault that I'm struggling to identify the root cause of, the surface cause is that the object pointer is empty but the root cause for why that object was empty when it should've had a...

I'm using mono because that's supposed to be the defacto standard on linux, also because it has unsupported stuff it's easier to program for both if I use it as primary.
As for IDE, I find IDEs get...

ty, wish I'd though of the linux man pages, oh well, at least I now have a lot more info I didn't have before

I haven't been able to find information on that, yet I vaguely remember reading somewhere it meant the length of the passed string, is that correct?

So far this is how I'm treating the modifiers in my custom implementation:



/* Defaults used if %> is not used to switch to another set
*
* In all cases these modifiers are read directly...

I'm trying to make sure I can compile C# on my manjaro install (for job hunting purposes) and I would like to know what are the common defines used, for example C uses CC for the compiler, C++ CXX...

But if I don't ask he might not think to elaborate, if he still refuse to elaborate then he's only showing himself to be "not worthwhile", by God's own words, no matter how many times we are wronged,...

What makes you say that? And of whom are you referring? Even when I look at the initial post of the thread I see nothing that really deviates form the title, might've confounded the question a bit...

*looks at thread title* "Which way to loop throught an array is the fastest one?"
I believe you're incorrect there, unless someone changed the title before I saw the thread.

From what I see I think you're misunderstanding what sizeof does, for starters sizeof(commands) will, in general, be equal to sizeof(int), that is the sizeof of what will contain the values of your...

I've not read through the posts here but I'll add my tidbit. I remember watching a vid at some point that mentioned going backwards through an array is usually faster than going forwards, something...

I've got a C api that has a lot of common behaviour typedefs (namely the char, wchar_t, char16_t etc lot), I've managed to do this so far:

string.cpp


#ifdef INC_PAW
#include...

When you're just experimenting with C code or making a software version (albeit not as fast as hardware) the preprocessor macros & the pointers are useful, besides you can always just preparse the...

Welp that bit operation flexibility is beyond my ability to fix, for that particular example I'd say a temporary macro would be suitable:


uint32_t tausworthe_via_pointers(uint32_t *s1, uin32_t...

Well I consider apathy close enough to agreement in that you're not disagreeing so that's good enough for me, I wouldn't expect the library to solve your needs when I'm currently writing it for my...

Er, no I don't see the C library as being exclusively for consoles, that just happens to be the easiest place to start since what I'm aiming to move onto before I take the detachment from CRT...

Thanks but I'm already aware of those differences, guessing I didn't make it clear but I sorted the issue after finding out I had been returning the wrong count of printed characters from...