[fpc-pascal] Re: Fatal error "Executable image size is too big for wince target"

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 NOSPA

[fpc-pascal] URIParser

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 accordin

[fpc-pascal] Re: URIParser

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); writeln(#9'Ho

Re: [fpc-pascal] Re: URIParser

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. Mi

Re: [fpc-pascal] Re: URIParser

On Wed, May 18, 2011 at 15:50, 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 http://sip:

Re: [fpc-pascal] Re: URIParser

On Wed, 18 May 2011, ik wrote: On Wed, May 18, 2011 at 15:50, 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 http://sip:

RE : [fpc-pascal] Re: URIParser

>> 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 S

Re: [fpc-pascal] Re: URIParser

In our previous episode, michael.vancann...@wisa.be said: > > > > RFC 3986 does talk about such structure > > of URI as well. > > Hmmm. > > How can code distinguish between > > protocol:something@somesite > > and > password:something@somesite > > ? The sec

RE : [fpc-pascal] Re: URIParser

> 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 : fpc-pasc

Re: [fpc-pascal] Re: URIParser

On Wed, May 18, 2011 at 16:08, Marco van de Voort wrote: > In our previous episode, michael.vancann...@wisa.be said: > > > > > > RFC 3986 does talk about such > structure > > > of URI as well. > > > > Hmmm. > > > > How can code distinguish between > > > > prot

Re: [fpc-pascal] Re: URIParser

On Wed, 18 May 2011, ik wrote: On Wed, May 18, 2011 at 16:08, Marco van de Voort wrote: In our previous episode, michael.vancann...@wisa.be said: RFC 3986 does talk about such structure of URI as well. Hmmm. How can code distinguish between proto

Re: [fpc-pascal] Re: URIParser

On Wed, May 18, 2011 at 16:49, wrote: > > > On Wed, 18 May 2011, ik wrote: > > On Wed, May 18, 2011 at 16:08, Marco van de Voort >> wrote: >> >> In our previous episode, michael.vancann...@wisa.be said: >>> > RFC 3986 does talk about such > >>>

Re: [fpc-pascal] Re: URIParser

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:

Re: [fpc-pascal] Re: URIParser

On Wed, 18 May 2011, ik wrote: On Wed, May 18, 2011 at 16:49, 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 sip::mysecr...@mydomain.com according t

[fpc-pascal] Re: PDFlib TET - convert using h2pas

On Tue, May 17, 2011 at 5:04 PM, Marcos Douglas 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 translat

Re: [fpc-pascal] Re: PDFlib TET - convert using h2pas

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

RE : [fpc-pascal] Re: URIParser

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

Re: [fpc-pascal] Re: PDFlib TET - convert using h2pas

On Wed, May 18, 2011 at 11:26 AM, Felipe Monteiro de Carvalho wrote: > The file is not big, why don't you just convert it manually? There are 2 reasons: 1- I do not know C very well. 2- Because the first reason, maybe I expended much time to do this. I would like the help of h2pas tool. Thanks,

Re: [fpc-pascal] Re: PDFlib TET - convert using h2pas

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

Re: [fpc-pascal] Re: PDFlib TET - convert using h2pas

On Wed, May 18, 2011 at 11:37 AM, Felipe Monteiro de Carvalho 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 use another language with support

Re: RE : [fpc-pascal] Re: URIParser

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 wit

RE : [fpc-pascal] Re: PDFlib TET - convert using h2pas

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

Re: RE : [fpc-pascal] Re: URIParser

On Wed, May 18, 2011 at 17:56, wrote: > > > 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;u

Re: [fpc-pascal] Re: PDFlib TET - convert using h2pas

On Wed, May 18, 2011 at 4:43 PM, Marcos Douglas 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 > http://www.pdflib.com/products/tet/how-to-use-tet

RE : RE : [fpc-pascal] Re: URIParser

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 : sip:+1-212-555-1212:1.

RE : RE : [fpc-pascal] Re: PDFlib TET - convert using h2pas

>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 (po

Re: [fpc-pascal] Re: PDFlib TET - convert using h2pas

On Wed, May 18, 2011 at 12:05 PM, Felipe Monteiro de Carvalho wrote: > > On Wed, May 18, 2011 at 4:43 PM, Marcos Douglas 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,

Re: RE : RE : [fpc-pascal] Re: PDFlib TET - convert using h2pas

On Wed, May 18, 2011 at 1:28 PM, Ludo Brands 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 previous message)

RE : RE : RE : [fpc-pascal] Re: PDFlib TET - convert using h2pas

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 - convert

Re: RE : RE : RE : [fpc-pascal] Re: PDFlib TET - convert using h2pas

On Wed, May 18, 2011 at 2:43 PM, Ludo Brands 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 - fpc-pascal@lists.freepasca

RE : RE : RE : RE : [fpc-pascal] Re: PDFlib TET - convert using h2pas

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.

Re: RE : RE : RE : RE : [fpc-pascal] Re: PDFlib TET - convert using h2pas

On Wed, May 18, 2011 at 3:12 PM, Ludo Brands 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 looking at > the h

Re: RE : [fpc-pascal] Redirecting input to a child process

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- >

[fpc-pascal] Re: ERROR compile revision 17494 /fixes_2_4

On Wed, May 18, 2011 at 4:24 PM, Marcos Douglas 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 - fpc-pascal@list

Re: [fpc-pascal] Re: ERROR compile revision 17494 /fixes_2_4

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)

Re: [fpc-pascal] Re: ERROR compile revision 17494 /fixes_2_4

On Wed, May 18, 2011 at 4:53 PM, Marco van de Voort 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 y

Re: [fpc-pascal] Re: ERROR compile revision 17494 /fixes_2_4

On Wed, May 18, 2011 at 4:57 PM, Marcos Douglas wrote: > On Wed, May 18, 2011 at 4:53 PM, Marco van de Voort 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 tr

Re: [fpc-pascal] Redirecting input to a child process

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 er

Re: [fpc-pascal] Redirecting input to a child process

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 cre

[fpc-pascal] 64 bit ?

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

[fpc-pascal] DateTimeToFileDate

If I do this on a Linux machine (Free Pascal Compiler version 2.4.2 [2010/11/08] for i386) WriteLn(DateTimeToFileDate(Now)); WriteLn(trunc((now-EncodeDate(1970,1,1))*86400)); I get this 1305786833 1305794033 There is a difference of 7200= 2 hours. Is this correct? I would not expect a di