Re: [fpc-devel] don't you think it's time to update delphi modecompatibility?

2005-05-27 Thread Bisma Jayadi
 Name one that really enables you to do something that you couldn't do
 otherwise.

Actually... none. :)

 If you want portability, simply don't use D2005 syntax.

Hmmm... very nice advice. :)

 Write it in D7 and compile it everywhere.

 To my knowledge there are no plans for post-D7 support. The whole point is
 compability with Delphi.NET, and there is not much interest in that anyway.

So, may I conclude that FPC is targetting D7 language compatibility? That's 
sound fair enough to me, and -thanks God- I can live with that. :)

Is the D7 compatibility has been reached fully or partially or still under 
development? How far the compatibility of FPC v.2.0 with D7? Is there any docs 
explain about this issue? Because I still failed to compile my D7 codes under 
FPC 2.0. It's an D7 codes utilizing dbExpress components.

-Bee-

has Bee.ography at:
http://beeography.modblog.com



___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel


Re: [fpc-devel] don't you think it's time to update delphi modecompatibility? - IDispatch, implements

2005-05-27 Thread Danny Milosavljevic
Hi,

Am Freitag, den 27.05.2005, 15:36 +0700 schrieb Bisma Jayadi:
  Name one that really enables you to do something that you couldn't do
  otherwise.
 
 Actually... none. :)
 
  If you want portability, simply don't use D2005 syntax.
 
 Hmmm... very nice advice. :)
 
  Write it in D7 and compile it everywhere.
 
  To my knowledge there are no plans for post-D7 support. The whole point is
  compability with Delphi.NET, and there is not much interest in that anyway.
 
 So, may I conclude that FPC is targetting D7 language compatibility? That's 
 sound fair enough to me, and -thanks God- I can live with that. :)
 
 Is the D7 compatibility has been reached fully or partially or still under 
 development? How far the compatibility of FPC v.2.0 with D7? Is there any 
 docs 

at least the (com) implements keyword and the variant IDispatch
compiler support is still missing, whereas someone wanted to tell me the
behaviour of the latter, but mysteriously vanished. Someone else started
to implement the implements keyword, I think.

For IDispatch, its something like if there is a variant (containing
a ??? IUnknown reference) used in an expression, and then a dot follows,
then pass the actual method name of the method called via idispatch to
the interface in the variant.

It's like
  i: IUnknown;
  v: Variant;

  i := mooo;
  v := i;
  v.Bla; --- magical auto-cast to IDispatch and passing 'Bla' to be
called to Invoke


HRESULT Invoke( 
  DISPID  dispIdMember,  
  REFIID  riid,  
  LCID  lcid,
  WORD  wFlags,  
  DISPPARAMS FAR*  pDispParams,  
  VARIANT FAR*  pVarResult,  
  EXCEPINFO FAR*  pExcepInfo,  
  unsigned int FAR*  puArgErr  
);
Use GetIDsOfNames or the object's documentation to obtain the dispatch
identifier.
---

Pretty sure I'm missing something (like for example what the dispids and
'dispatch interfaces' are for and such), and it makes no sense if we
dont have an user who uses IDispatch (since it then cant be really
tested, plus, on linux - where I am -, there are close to no apps that
support that IDispatch interface at all). Someone please fill in the
gaps.
(Plus, I hated IDispatch when I was using delphi. Very good for
variant-based runtime-only errors, hard to track down.)

 explain about this issue? Because I still failed to compile my D7 codes under 
 FPC 2.0. It's an D7 codes utilizing dbExpress components.

Hmm, well, more info please :)

 
 -Bee-
 
 has Bee.ography at:
 http://beeography.modblog.com

cheers,
   Danny

 
www.keyserver.net key id A334AEA6



signature.asc
Description: This is a digitally signed message part
___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel


Re: [fpc-devel] don't you think it's time to update delphi modecompatibility?

2005-05-27 Thread Marco van de Voort
 So, may I conclude that FPC is targetting D7 language compatibility? That's 
 sound fair enough to me, and -thanks God- I can live with that. :)

Roughly yes. That is the goal of the 2.0.x branch, languagewise.

 Is the D7 compatibility has been reached fully or partially or still under
 development? How far the compatibility of FPC v.2.0 with D7? Is there any
 docs explain about this issue? Because I still failed to compile my D7
 codes under FPC 2.0. 

_language_ compability. 

Some known missing functionality:
1 implements style delegation
2 vararray support is patchy.
3 customvariants are missing in the rtl
4 packages
5 dispinterfaces and dispid.
6 assembler routines have some constructs that are not supported.
   These are being eliminated at a fairly decent rate the last 
few months

Libraries are done on a case by case basis (is this part already legacy
in D6/D7, is it too OS specific etc).


___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel