Hi Lorenzo and all,
1) {} to enclose function's body. This valid code:
2) ";" as statement separator. This is a valid code:
3) "=" vs "==" vs ":="
Comments?
This wouldn't be Clipper anymore.
C-like syntax with Clipper-like high-levelness is
already implemented as C#.
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.
Brgds,
Viktor
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.
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
