Search:

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...

Never mind, turns out I had been returning a count that was 1 less than the actual count somehow, after abandoning the separate count I was doing - which added up the returned counts from the...

I get this:


...
pawPrintf( "%u", 10 ) gave:
10pawPrintf( "%d, %s", did, "abc" ) gave:
2, abc
...

From this:

Judging by the lack of responses I'm guessing nobody has any suggestion for increasing flexibility so I'll just bulldoze ahead with this api

So far this is how I'm declaring my custom versions:


typedef struct _PAWBUF PAWSTR;
typedef struct _PAW_PUTF PAW_PUTF;
typedef struct _PAW_GETF PAW_GETF;

struct _PAW_PUTF
{...

Never mind, found my solution:


#define INC_2X_H(INC) #INC
#define INC_1X_H(DIR,INC) INC_2X_H(DIR/INC)
#define INC_X_H(INC) INC_1X_H(INC_X,INC)

#include INC_X_H(...)

I'm using the header...

Okay, so I had an idea to work around the issue since macros are at least allowed:



#define INC_3X_H(INC) #INC
#define INC_2X_H(DIR,INC) INC_3X_H(DIR##INC)
#define INC_1X_H(DIR,INC)...

K, so I tried to make gcc generate absolute paths by defining a variable for where my headers are located and attempted to concatenate it like this:



gcc ... -D INC_X="\"./include/\"" ...
...

First the link, don't worry about the generated executables not running past a certain point, I only just finished getting the new lua build script to generate the needed goals for make to process,...

Never mind, finally spotted what I did wrong, I didn't realise I needed to minus 1 from the length of sfx, code now looks like this (I also noticed some left over code from experiments so fixed that...

I can extract directories with the below code just fine but arguments like "src/libbasic/*.c" aren't resulting in anything (yes there are c files in that directory), any ideas?


local function...

Just clone the below then run "make --just-print" in the root folder, in theory should work from any sub folder but I haven't gotten round to testing that as I still need to tweak rule output a bit...