[Harbour] Xbase++ go to visual fox pro

[Massimo Belgrano]

THis is a post of Steffen F. Pirsig regargind accept  the "." instead of the
":" in terms of OO syntax


>Peter,

>

> well to some extend you are right. However it should be noted

> that Clipper 5 with the Get and TBrowse objects introduced the

> : as the send operator to the language and bec. Xbase++ is designed

> to be 100% Clipper language compatible ...

>

> I agree with you in terms of other languages such as VB.NET or C#

> or ... but we are talking here about a "small" syntactical nuance -

> another option btw. would be to allow both send operators at the

> same point in time - so mixing both syntaxes. But that would give

> anybody the option to mix  and will create a big mess (IMO)

> in terms of code readability.

>

> Just a few 0.00001€ on that subject.

>

> With kind regards

> Steffen F. Pirsig

> Alaska Software Inc.



"Peter Alderliesten" <p.alderliesten at emergo-systems.nl> wrote in message

news:yjxzqlc9g1r0.858iyru33yxv$.dlg at 40tude.net...

> Steffen,

>

>>  3.) We also added a /fox switch to the Xbase++ compiler to accept

>>  the "." instead of the ":" in terms of OO syntax to make compilation of

>>  VFP code easier.

>

> I appreciate that attracting VFP-users is triggering this feature, but

> shouldn't you make the switch name more general. There are some Visual

> Basic users as well and perhaps some more...

> I always thought that using the "." was the standard send operator and

> that

> Xbase++ was off-key on this issue.

>

> Peter




2008/10/24 Przemyslaw Czerpak <druzus at acn.waw.pl>

> On Fri, 24 Oct 2008, Massimo Belgrano wrote:
>
> Hi Massimo,
>
>
>
> >  3.) We also added a /fox switch to the Xbase++ compiler to accept
> >  the "." instead of the ":" in terms of OO syntax to make compilation of
> >  VFP code easier.
>
> I though about adding such feature but in few cases it may cause
> unexpected results, f.e.:
>
>   x:=o:msg.and.x
>
> is valid Clipper code which can be written in more readable form:
>   x := o:msg .and. x
>
> If we add such extension then it should mean:
>
>   x := o:msg:and:x
>
> I do not like it. For me it's a bug in language definition.
> If it's will be very important for users then I can add support for it
> but not inside grammar rules but rather in PP or lexer and I will want
> to keep original Clipper operators precedence so 'and', 'or' and 'not' will
> be reserved method names. With such condition the above can be implemented
> by these _THRE_ lines inside complex.c.:
>
>      case HB_PP_TOKEN_DOT:
>         pLex->iState = OPERATOR;
>         return ':';
>
> In can be also done even now as simple PP directive:
>
>   #xtranslate <exp1>.<exp2> => <exp1>:<exp2>
>
> because Harbour accepts much marker at the beginning of match rule
> but this may interacts with 3-rd party code PP directives which use
> dot (.).
>
> >  4.) With UniversalSQL we are providing SQL for all DBEs which must
> >  be seen as the next evolutionary step of the way how VFP has supported
> > SQL
> >  for the DBF tables. In addition our goal here is to beat VFP in terms
> > of
> >  performance - which is not easy but we are right now at a very good
> > track
> >  to reach that point.
>
> I do not know VFP RDD performance but I heard from xbase++ users that
> [x]Harbour DBFCDX is much faster then CDXDBE.
>
> best regards,
> Przemek
> _______________________________________________
> Harbour mailing list
> Harbour at harbour-project.org
> http://lists.harbour-project.org/mailman/listinfo/harbour
>



-- 
Massimo Belgrano

Albo Nazionale Informatici Professionisti 2620
Socio 2843 Associazione Informatici prof.

Analisi e sviluppo software per Lan e Web
Consulenza informatica - Formazione
Delta Informatica S.r.l.  http://www.deltain.it
Via Torelli,31 - 28100 Novara - Tel: 0321/30281
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.harbour-project.org/pipermail/harbour/attachments/20081208/ffb616dc/attachment.html