In article <391f429b-4cb8-4762-80bf-511a1dc5eeab@a2 9g2000pra.googl egroups.com>,
Tomás Ó hÉilidhe <toe@lavabit.co mwrote:
First, I haven't analyzed your code in depth, and I don't really care
about the minutiae. I leave that to the pedants^Wlangua ge lawyers.
However, if I were doing this, I'd do it the other way around. That is,
I'd call one of the vs*tf*() functions once, at the beginnning, to
expand out the %(s). Then, I'd go back and parse the string - handling
the color coding stuff via my function, and printf'ing the rest.
Tomás Ó hÉilidhe <toe@lavabit.co mwrote:
>
>Firstly... before the guns go off... I realise that the C Standard
>doesn't mention anything about the existence of colour, which is why
>I'm writing a small little cross-platform library for setting the
>console text colour. It'll have a function like as follows:
>Firstly... before the guns go off... I realise that the C Standard
>doesn't mention anything about the existence of colour, which is why
>I'm writing a small little cross-platform library for setting the
>console text colour. It'll have a function like as follows:
about the minutiae. I leave that to the pedants^Wlangua ge lawyers.
However, if I were doing this, I'd do it the other way around. That is,
I'd call one of the vs*tf*() functions once, at the beginnning, to
expand out the %(s). Then, I'd go back and parse the string - handling
the color coding stuff via my function, and printf'ing the rest.
Comment