Jonas Maebe wrote:
What you can try is to compile the LCL without debug information (add
the option -g- for the LCL compilation)
Thank you for your answer, I will give it a try.
Greetings
--
Björn Schreiber, DRIGUS GmbH
news...@drigus.de
Bei Email NOSPAM in den Betreff aufnehmen.
Put
Hello,
I have tried to use the URIParser on a structure like so:
sip:ik@10.0.0.2:5060;name=test?header=something
That's the most complicated SIP URI according to the RFC (3261).
But the record was able to just return to me the protocol (sip) and nothing
else.
Does the unit implement it
I've created a more simple example:
program uri_test;
uses URIParser;
var
URI : TURI;
begin
URI := ParseURI('sip:b...@example.com');
writeln('URI:');
writeln(#9'Protocol: ', URI.Protocol);
writeln(#9'Username: ', URI.Username);
writeln(#9'Password: ', URI.Password);
On Wed, 18 May 2011, ik wrote:
I've created a more simple example:
program uri_test;
uses URIParser;
var
URI : TURI;
begin
You don't specify the protocol.
a URI starts always with protocol://
so http://sip:b...@example.com/
The URIParser unit expects the protocol to be in place.
On Wed, May 18, 2011 at 15:50, michael.vancann...@wisa.be wrote:
On Wed, 18 May 2011, ik wrote:
I've created a more simple example:
program uri_test;
uses URIParser;
var
URI : TURI;
begin
You don't specify the protocol.
a URI starts always with protocol://
so
On Wed, 18 May 2011, ik wrote:
On Wed, May 18, 2011 at 15:50, michael.vancann...@wisa.be wrote:
On Wed, 18 May 2011, ik wrote:
I've created a more simple example:
program uri_test;
uses URIParser;
var
URI : TURI;
begin
You don't specify the protocol.
a URI starts always with
a URI starts always with protocol://
RFC 2396 (http://tools.ietf.org/html/rfc2396 ) specifies that an URI has to
start with the protocol and a colon. The // depends on the protocol scheme.
Valid URI's are for example mailto:mdue...@ifi.unizh.ch or
news:comp.infosystems.www.servers.unix. The SIP
In our previous episode, michael.vancann...@wisa.be said:
RFC 3986 http://tools.ietf.org/html/rfc3986 does talk about such structure
of URI as well.
Hmmm.
How can code distinguish between
protocol:something@somesite
and
password:something@somesite
?
The second is not an uri
How can code distinguish between
protocol:something@somesite
and
password:something@somesite
Protocol is missing from the last one = not an URI. A protocol is asumed.
Browsers assume http:, mailers mailto:, telnet assumes telnet:, etc
Ludo
-Message d'origine-
De :
On Wed, May 18, 2011 at 16:08, Marco van de Voort mar...@stack.nl wrote:
In our previous episode, michael.vancann...@wisa.be said:
RFC 3986 http://tools.ietf.org/html/rfc3986 does talk about such
structure
of URI as well.
Hmmm.
How can code distinguish between
On Wed, 18 May 2011, ik wrote:
On Wed, May 18, 2011 at 16:08, Marco van de Voort mar...@stack.nl wrote:
In our previous episode, michael.vancann...@wisa.be said:
RFC 3986 http://tools.ietf.org/html/rfc3986 does talk about such
structure
of URI as well.
Hmmm.
How can code distinguish
On Wed, May 18, 2011 at 16:49, michael.vancann...@wisa.be wrote:
On Wed, 18 May 2011, ik wrote:
On Wed, May 18, 2011 at 16:08, Marco van de Voort mar...@stack.nl
wrote:
In our previous episode, michael.vancann...@wisa.be said:
RFC 3986 http://tools.ietf.org/html/rfc3986 does talk
It should assume that sip is a protocol, like it does now.
I think that:
URI := ParseURI('sip:b...@example.com');
Should output this:
Protocol: sip
Username: bob
Password:
Host: example.com
Port: 0
Path:
Document:
Params:
On Wed, 18 May 2011, ik wrote:
On Wed, May 18, 2011 at 16:49, michael.vancann...@wisa.be wrote:
So, how to distinguish between the two ?
sip:mysec...@mydomain.com
Is sip the protocol or the user name for a HTTP address ?
sip is the protocol, mysecrect is the user name
On Tue, May 17, 2011 at 5:04 PM, Marcos Douglas m...@delfire.net wrote:
Hi,
I would like to use the TET[1] in FPC on Windows.
There are 2 options:
1- Translate C header to use libtet.dll (I prefer);
2- Use the COM object (TET_com.dll);
I can use COM in Delphi 7 easily. There is a Wizard to
The file is not big, why don't you just convert it manually?
--
Felipe Monteiro de Carvalho
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Problem is that the RFC definition for the URI doesn't specify the
individual protocol scheme. So every protocol can specify it's own stuff.
Take the general sip URI:
sip:user:password@host:port;uri-parameters?headers. User can be a telephone
number with folowing definition: global-phone-number
If you have any question about translating manually I can help.
--
Felipe Monteiro de Carvalho
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
On Wed, May 18, 2011 at 11:37 AM, Felipe Monteiro de Carvalho
felipemonteiro.carva...@gmail.com wrote:
If you have any question about translating manually I can help.
OK, thank you!
Answer me: if you were to use this lib, which way do you choose?
ActiveX (Delphi or FPC), translate header or
On Wed, 18 May 2011, Ludo Brands wrote:
Problem is that the RFC definition for the URI doesn't specify the
individual protocol scheme. So every protocol can specify it's own stuff.
Take the general sip URI:
sip:user:password@host:port;uri-parameters?headers. User can be a telephone
number
In this case:
1) because h2pas doesn't use pascal macro's. A construct like
#if defined(WIN32) !defined(PDFLIB_CALL)
#define PDFLIB_CALL __cdecl
#endif
can not be translated using pascal constants or functions. Cdecl is a
calling convention modifier.
2) afaik pascal doesnt support widestring
On Wed, May 18, 2011 at 4:43 PM, Marcos Douglas m...@delfire.net wrote:
Answer me: if you were to use this lib, which way do you choose?
ActiveX (Delphi or FPC), translate header or use another language with
support (Java, .NET, Pyhon, Perl, etc... see here
The differences I mentioned are just the tip of the iceberg. Another
example: the RFC definition for URI permits for every scheme to define their
own character escape sequence for special and non ascii-characters. Guess
what: sip allows reserved characters in the user field :
From your question COM or header, I assumed you are only interested in
windows. I also assume that you don't want to export functions defiend. So,
I did the following:
- removed PDFLIB_API and PDFLIB_CALL (point 1 in my previous message)
- replaced the L.. defines by one to the char version
On Wed, May 18, 2011 at 12:05 PM, Felipe Monteiro de Carvalho
felipemonteiro.carva...@gmail.com wrote:
On Wed, May 18, 2011 at 4:43 PM, Marcos Douglas m...@delfire.net wrote:
Answer me: if you were to use this lib, which way do you choose?
ActiveX (Delphi or FPC), translate header or use
On Wed, May 18, 2011 at 1:28 PM, Ludo Brands ludo.bra...@free.fr wrote:
From your question COM or header, I assumed you are only interested in
windows. I also assume that you don't want to export functions defiend. So,
I did the following:
- removed PDFLIB_API and PDFLIB_CALL (point 1 in my
Here you go,
Ludo
-Message d'origine-
De : fpc-pascal-boun...@lists.freepascal.org
[mailto:fpc-pascal-boun...@lists.freepascal.org] De la part de Marcos
Douglas
Envoyé : mercredi 18 mai 2011 19:37
À : FPC-Pascal users discussions
Objet : Re: RE : RE : [fpc-pascal] Re: PDFlib TET -
On Wed, May 18, 2011 at 2:43 PM, Ludo Brands ludo.bra...@free.fr wrote:
Here you go,
Now I can learn a bit more about C language, comparing your header
file with my (incomplete) header file.
Thanks,
Marcos Douglas
___
fpc-pascal maillist -
Remember, what I did was just educated arm twisting the input file so that
h2pas could understand the input and do the bulk of the work. There is still
quite some work to do after on the pp file. Some can be done from looking at
the header file only, others need a better knowledge of the API.
On Wed, May 18, 2011 at 3:12 PM, Ludo Brands ludo.bra...@free.fr wrote:
Remember, what I did was just educated arm twisting the input file so that
h2pas could understand the input and do the bulk of the work. There is still
quite some work to do after on the pp file. Some can be done from
A little update on the subject.
Ludo Brands wrote:
If you run 'more' in a cmd window you'll notice that
'more' echoes the input but only sends to stdout when a
return is entered. I modified the program to send
'Anton'#10 and the program reads back 'Anton'#10 from std-
out.
On Wed, May 18, 2011 at 4:24 PM, Marcos Douglas m...@delfire.net wrote:
Hi,
I updated my FPC to revision 17494, a couple minutes ago.
In attachment there is a log of erros.
In trunk is OK...
Can you help?
Marcos Douglas
___
fpc-pascal maillist -
In our previous episode, Marcos Douglas said:
I updated my FPC to revision 17494, a couple minutes ago.
In attachment there is a log of erros.
In trunk is OK...
Can you help?
here is something wrong with your path statements, and a MAKE of a different
toolchain (Microsoft, borland) is
On Wed, May 18, 2011 at 4:53 PM, Marco van de Voort mar...@stack.nl wrote:
In our previous episode, Marcos Douglas said:
I updated my FPC to revision 17494, a couple minutes ago.
In attachment there is a log of erros.
In trunk is OK...
Can you help?
here is something wrong with
On Wed, May 18, 2011 at 4:57 PM, Marcos Douglas m...@delfire.net wrote:
On Wed, May 18, 2011 at 4:53 PM, Marco van de Voort mar...@stack.nl wrote:
In our previous episode, Marcos Douglas said:
I updated my FPC to revision 17494, a couple minutes ago.
In attachment there is a log of
Ludo Brands:
You can file a bug at http://bugs.freepascal.org/.
This is bug #0019325.
...
I thought about writing a patch, but it seems that it is not
enough to modify the implementation of the Windows-specific
pipes.inc.
The correct way to create pipes for the three channels (out,
in and
On Thu, 19 May 2011, Anton Shepelev wrote:
Ludo Brands:
You can file a bug at http://bugs.freepascal.org/.
This is bug #0019325.
...
I thought about writing a patch, but it seems that it is not
enough to modify the implementation of the Windows-specific
pipes.inc.
The correct way to
I have a desktop with a 64bit AMD x4 Phenom processor. I have noticed
that FreePascal programs perform worse on this computer then they do on
my 32 bit laptop. Integer performance seems to be about 3 times worse
then on the laptop. Now if I convert the pascal source to c and compile
that as
38 matches
Mail list logo
