The problem is that "Global" is now a reserved word.  I filed a bug report
but RS said this was not a bug and closed it.

   I disagree.  I feel the error message should tell you that Global was a
reserved word.  Goes to show you I don't know anything.

   I had to change my module named "Global" to a module named "Globals" and
change every instance of "Global." in my code to "Globals."  That fixed it.

   In addition, 2007R2 under Linux incorrectly interprets 2007R2 projects
created in Macintosh. It screws them up during load.  Luckily, the previous
version can read the 2007R2 project, as long as new features aren't being
used.  I'm back on 2007R1 for now.

wade




Subject: RB 2007R2 Syntax

One of my projects that compiled perfectly on R1 has suddenly developed a
syntax error in R2 on my Mac (Intel 2.66ghz). Someplace.

When I try to ?run? the code, RB stops, shows me a window that says:

An error has occurred while compiling this project.
Message: Syntax error.
File: PeanutsRUs.rbp
Location: Global
Code:

I assume the error is in my ?Global? module. However the ?blank? code
reference doesn?t help much. I went through every subroutine and commented
it out. So all the routines were there, they just didn?t do anything. Still
wouldn?t compile.

Saved it as an XML project, reloaded it, same error.

Tossed Rb2007R2 in the trash, removed all the prefs for it, redownloaded it,
same error.

There are a number of constants and properties in the module as well.

One other thing, when I first started RB 2007R2 I got an unhandled NilObject
in the REALPluginMain. Something about Compiler.ResolveSymbolTables yadda
yadda yadda. The error said to quit, which apparently when you are compiling
you can?t (least I couldn?t, clicking Quit simply keep compiling).

Any suggests as to how to narrow this thing down?

Mel
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>

Reply via email to