gbadev.org forum archive

This is a read-only mirror of the content originally found on forum.gbadev.org (now offline), salvaged from Wayback machine copies. A new forum can be found here.

DS development > Error: expected ')' before ';' token in main function

#172248 - mikedpw0 - Wed Jan 27, 2010 4:04 am

This sounds like an error you'd get from a silly typo. However there's not much code in my main function and what's there appears to be correct.

Here is the main function that generates the error:

nt main() {

/* Turn on the 2D graphics core */
powerOn(POWER_ALL_2D);

/* Configure the VRAM and BG control registers */
lcdMainOnBottom();
initVideo();
initBackgrounds();

/* Display the backgrounds */
displayStarField();
displayPlanet();
displaySplash();

return 0;
}

Why the heck would this be generating such an error? None of the functions from lcdMainOnBottom() onward take any arguments so its not like the compiler should be expecting any. It must be expecting me to use powerOn() (the only function derived from ndslib rather than my own functions) differently? This is exactly how it is used in the tutorial I am following, though (patater's tutorial, that is).

I've checked and checked again. With the exception of some comments, my main function is identical to the tutorial. Could an error in another function be causing this? And wouldn't the compiler mention that function if that were the case?

The hell is going on?

All I can think is that this tutorial is outdated and that powerOn() function is expecting something that it didn't need in an earlier version of devkitpro.

#172249 - zeruda - Wed Jan 27, 2010 4:12 am

Cursory glance and I see

nt main() {
should be
int main() {

#172250 - mikedpw0 - Wed Jan 27, 2010 4:15 am

zeruda wrote:
Cursory glance and I see

nt main() {
should be
int main() {


Haha. That's a copy-paste error. The actual code is right.

However, I did figure out the problem and wish I could delete this thread now. Because I was only seeing part of a bigger error when running 'make'. The error was, in fact, in another function, and was indeed a stupid typo. sorry for wasting the forum space.