Hi,

Interface's (iUnknown) support in Linux, or only Windows support them?

Thanks.

you wrote

Hi, Interface's (iUnknown) support in Linux, or only Windows support them?

Of course under Linux as well. What would IUnknown prevent from working with Linux?

I writing DirectX's filter (DirectShow). I need make Linux version. I think, i have big problem :(

you wrote

I writing DirectX's filter (DirectShow). I need make Linux version. I think, i have big problem :(

Well, DirectShow is another story than IUnknown :) I've no idea how and if DirectShow
can be emulated with Linux...

:-)

DirectShow filter use iUnknown-like interface's for normal working. If Fpc support interface's, then, i think, i can write filter under Linux? =)

Or what?

Well, yes and no. IUnknown is supported and it has a method QueryInterface as well. But the question is which interfaces can be "queried" ...

:-) DirectShow filter use iUnknown-like interface's for normal working. If Fpc support interface's, then, i think, i can write filter under Linux? =)

of course you can implement DirectShow filters on any platform, as a filter is just a COM object which implements certain interfaces. But you cannot use the filters delivered with DirectShow, obviously.

- Sebastian

Michail A.Baikov schrieb: > :-) > > DirectShow filter use iUnknown-like interface's for normal working. If

Fpc

Excuse me, but have M$ made DirectX for *NIX?

---
WBR, Max Artemev.
Mathematical department of the Pedagogic University of Moscow, Russia. The Raccoons Homepage http://theraccoons.lionking.ru [Furry] [Pascal++] [*NIX]

Excuse me, but have M$ made DirectX for *NIX?

no, but COM interfaces are just declarations, so they cannot be bound to an specific operating system.

(Wine/WineX has limited DX support on Linux, however)

- Sebastian

Pavel V. Ozerski wrote

At it is shown, there are exust two problems: 1) a procedural variable cannot be absolute to other variable;

This may be a real problem.

2) access to address of procedural variable using @@ is not supported.

You have to use TP or Delphi mode to use this syntax, FPC mode uses another (more clean imho) set of rules. See the manual for more info.

Jonas

This program compiled with Delphi works fine but cannot be compiled with FPC 1.1 (build 2002/08/01):

{$apptype console}
function xx:longint;
 begin
  xx:=1;
 end;
type
 txx=function:longint;
var
 x:txx;
 p:pointer;
 y:pointer absolute x; //causes FPC compiler error message
begin
 ;
 p:=pointer(x);//xx result typecasting
 writeln(longint(p));
 ;//xx entry point;
 writeln(longint(p));
 ;//xx entry point;
 writeln(longint(p));
 ;//address of x variable;
 writeln(longint(p));
 p:=@@x;//address of x variable, causes FPC compiler error message
 writeln(longint(p));
end.

At it is shown, there are exust two problems: 1) a procedural variable cannot be absolute to other variable; 2) access to address of procedural variable using @@ is not supported.BTW, using addr(@x) also causes compiler error message.

Sincerely, Pavel V. Ozerski.

P.S. I don't submit this report into bug list because I didn't test this sample with official 1.0.x releases.