RE: [Onboardc-project] Defining Macros.

[Blake W. <bw...@la...>]

> On 9/4/05, Blake Winton <bw...@la...> wrote:
> > As I mentioned in a post to the Yahoo Group, I'm trying to compile
> > PalmCUnit with OnBoardC.  I ran into a bug dealing with macros with
> > empty argument lists, and posted a pseudo-patch which 
> > should have dealt with it.
> Thanks again for that, it's nice to have someone take the time to fix
> a problem for themself.

Heh.  That's what happens when my mailserver decides to stop working.
But surely you see more of that than other open-source projects, what
with all you users by definition knowing the language you used to write
the code.  :)

> > I worked around it for the time being by adding an ununsed dummy
> > argument, but now I'm running into another couple of 
> > missing features which are totally blocking me.
> I'd suggest removing the parens from the macro definition if no
> arguments are intended.

Well, yeah, I could do that, but I really want it to look like a
function call.  (It's the "FAIL()" pseudo-method in the Test Framework.)

> It would be nice to add these features. Could you add them as feature
> requests on the sourceforge page, so we can keep track of them?
> http://sourceforge.net/tracker/?atid=478289&group_id=55794

I will, but I might take a crack at them before I do.

> For the first one (concatenating string constants), take a look at
> compile.c, ~line 3009. (Search for DoubleQuote), which is where quoted
> strings are handled.
> 
> For the # preprocessor operator, you probably need to look at the
> macro argument expansion code, in OnBoardC.c (which you've already
> looked at it seems...)

Cool, I'll see what I can do in there, after I get it all set up.

> Again, we'd love to have you on the team, if you're interested in
> helping out by contributing.

I'm glad to submit patches when I can, but please don't put me on
the team.  I'm already on six or seven teams that I only submitted
a couple of patches to.  ;)

Ah, what the hell.  Add me (I think I'm bwinton on sourceforge), and
when the sourceforge site is back up, I'll add the feature requests,
and assign them to myself.  I can't promise that I'll have much time
to work on OBC, at least until another problem bugs me, but it doesn't
hurt to be on the list, right?

What else would you need to know?  My policy should be:
I-abstain-unless-I-officially-vote and I promise to abide by the rest
of the rules listed in section 3 of the Charter.

Thanks,
Blake.