Re: [fpc-pascal] TP compatibility: procedural type

In our previous episode, Anton Shepelev said: > and the built-in TP documentation: > > http://putka.upm.si/langref/turboPascal/ > > Neither source makes any exceptions about the 'far' > and 'near' reserved words. Thence I concluded that > even though on some platforms these concepts may be

Re: [fpc-pascal] FPHTTPClient OpenSSL implementation

2. option don't resolve "screen capture software" warning in enterprise, and I found this from doc: "RAND_event() and RAND_screen() are deprecated since OpenSSL 1.1.0. Use the functions described above instead." https://www.openssl.org/docs/man1.1.0/crypto/RAND_screen.html so 1.option will

Re: [fpc-pascal] TP compatibility: procedural type

Am 29.08.2017 18:48 schrieb "Anton Shepelev" : > I now see from other replies that the -Mtp mode > helps compile TP programs in FPC but not vice versa, > which makes me wonder why pointer arithmetics is so > limited in -Mtp that one must use Inc and Dec in- > stead of

Re: [fpc-pascal] TP compatibility: procedural type

Karoly Balogh to Anton Shepelev: >>But this is from the Language guide -- a document >>that descrbes the language in a platform-agnostic >>way... > >Then you have a very different TP manual than me. >Mine is really only for the specific 16-bit case, >and there is no platform agnostic

Re: [fpc-pascal] TP compatibility: procedural type

In our previous episode, Anton Shepelev said: > But this is from the Language guide -- a document > that descrbes the language in a platform-agnostic > way Then you have a very different TP manual than me. Mine is really only for the specific 16-bit case, and there is no platform

Re: [fpc-pascal] TP compatibility: procedural type

Am 29.08.2017 14:26 schrieb "Anton Shepelev" : > > Karoly Balogh to Anton Shepelev: > > >>According to Borland's official language guide to > >>Turbo Pascal 7.0, > >> > >> To be used as procedural values, procedures and > >> functions must be declared with a 'far' directive

Re: [fpc-pascal] TP compatibility: procedural type

Karoly Balogh to Anton Shepelev: >>According to Borland's official language guide to >>Turbo Pascal 7.0, >> >> To be used as procedural values, procedures and >> functions must be declared with a 'far' directive >> or compiled in the '{$F+}' state. >> >>whereas Free Pascal in -Mtp seems to

Re: [fpc-pascal] TP compatibility: procedural type

Hi, On Tue, 29 Aug 2017, Anton Shepelev wrote: > >> To be used as procedural values, procedures and > >> functions must be declared with a 'far' direc- > >> tive or compiled in the '{$F+}' state. > >> > >>whereas Free Pascal in -Mtp seems to accept any > >>non-system procedure or

Re: [fpc-pascal] TP compatibility: procedural type

Sven Barth to Anton Shepelev: >>According to Borland's official language guide to >>Turbo Pascal 7.0, >> >> To be used as procedural values, procedures and >> functions must be declared with a 'far' direc- >> tive or compiled in the '{$F+}' state. >> >>whereas Free Pascal in -Mtp seems to

Re: [fpc-pascal] TP compatibility: procedural type

Am 29.08.2017 11:10 schrieb "Anton Shepelev" : > > Hello, all. > > According to Borland's official language guide to > Turbo Pascal 7.0, > > To be used as procedural values, procedures and > functions must be declared with a 'far' directive > or compiled in the

Re: [fpc-pascal] Freepascal Floating Point Issue

Am 29.08.2017 08:35 schrieb "Michael Schnell" : > > On 28.08.2017 08:04, Sven Barth via fpc-pascal wrote:I don't understand why we will have no more the right to use it under x64 OS... >> >> >> Because Microsoft declared it as deprecated. That means that should Microsoft ever

[fpc-pascal] TP compatibility: procedural type

Hello, all. According to Borland's official language guide to Turbo Pascal 7.0, To be used as procedural values, procedures and functions must be declared with a 'far' directive or compiled in the '{$F+}' state. whereas Free Pascal in -Mtp seems to accept any non- system procedure

[fpc-pascal] FPHTTPClient OpenSSL implementation

Hi, For years I'm working with synapse (Ararat) with OpenSSL and there  is same openssl.pas lib. So problem is with: in InitSSLInterface:     if assigned(_RandScreen) then   _RandScreen; and method: procedure RandScreen; begin if InitSSLInterface and Assigned(_RandScreen) then    

Re: [fpc-pascal] Freepascal Floating Point Issue

On 28.08.2017 08:04, Sven Barth via fpc-pascal wrote:I don't understand why we will have no more the right to use it under x64 OS... Because Microsoft declared it as deprecated. That means that should Microsoft ever bring out a 64-bit only OS ... In fact this still is a (mere) portability

Re: [fpc-pascal] Freepascal Floating Point Issue

On 28.08.2017 00:23, Ched wrote: But sometimes, we absolutely need numerical precision, so we have to assume the costs in terms of runtime and possibly nonportability. I understand that when compiling to an x32 32 Bit executable, 80 Bit Extended should be fine. -Michael