On Wed, Oct 1, 2008 at 1:01 PM, Szakáts Viktor <[EMAIL PROTECTED]> wrote:
> If the goal is to make Harbour compatible with Eclipse, > IMO one should rather try to contribute the relevant > parts to the Eclipse project itself, instead of changing > the Clipper language to fit into their existing concept. > Maybe it's just a matter of creating a syntax-rule file. This was my first idea. I've contacted a Java developer but he told me that it's not a trivial task. Language plugins are not only about syntax coloring but also outlining, source refactoring and so on. You need to know well the specific platform ( Eclipse is different from NetBeans ) not only Java. But this apart the "=" vs ":=" and the semicolon issues are general issue that will only improve the acceptance of the language. > PS: Just slightly related, but I'd rather find it useful > to add some switches to the compiler to warn on > obsolete, non-recommended/ambiguous or unnecessary > syntax alternatives, like '=' used as assignment. If we > are to clean or change the language syntax that is, and > drive language users to a better and more coherent syntax > style. Some other candidtates: if(), .not., <>, #, */&& comments. > Notice: Many of these come from dBase III+/Clipper <=87 > times, and the only reason they are there is compatibility > with such dinosaur code. Clearly I think the contrary for ":=" vs "=": it is the ":=" that should be ALWAYS like "=". best regards, Lorenzo _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
