Does anyone know why I have issues using ^ in a filename on windows systems?
Everything works fine if I just run my program and open the file with a ^ in
it, the issue I am having is when sending the filename in as a parameter. If
I set my parameter to File^name then Paramstr(1)= FileName.
This may be off-topic, but anyway:
I did some graphics programming in the 1990s (for customers of mine),
but with not so much interest on display terminals, but instead on large
plotters (DIN A0 format, for example).
I used a library called GKS at that time (graphics kernel system), which
was
Michael,
Permission granted. After using FPC to produce our first Windows 64-bit
library, and then using it to produce Linux libraries, I am happy to
contribute something back.
Cheers,
Alan
On Wed, May 8, 2019 at 2:22 PM Michael Van Canneyt
wrote:
>
>
> On Wed, 8 May 2019, Alan Krause
On Wed, 8 May 2019, Alan Krause wrote:
FPC Community,
Over the weekend I looked into AWS Lambda function custom runtimes, with
the hope of being able to create one using Free Pascal. I'm happy to say
that I have it up and running, and it produces a very small and quick
runtime perfect for
FPC Community,
Over the weekend I looked into AWS Lambda function custom runtimes, with
the hope of being able to create one using Free Pascal. I'm happy to say
that I have it up and running, and it produces a very small and quick
runtime perfect for AWS.
For sample code, please take at look at
On Wed, 8 May 2019, Dennis wrote:
I believe the red text below (in the url on the subject line) should be
AnsiIndexText instead of AnsiIndexStr.
Description
AnsiIndexStr matches AText against each string in AValues . If a match
is found, the corresponding index (zero-based) in the
I believe the red text below (in the url on the subject line) should be
AnsiIndexText instead of AnsiIndexStr.
Description
AnsiIndexStr matches AText against each string in AValues . If a match
is found, the corresponding index (zero-based) in the AValues array is
returned. If no match
On 08/05/2019 12:58 pm, Michael Van Canneyt wrote:
> Can you please create a bugreport so I will not forget ?
No problem.
https://bugs.freepascal.org/view.php?id=35542
Regards,
Graeme
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
On Wed, 8 May 2019, Graeme Geldenhuys wrote:
Hi,
https://www.freepascal.org/docs-html/rtl/sysutils/longrec.html
I'm referring to the documentation shown in the URL above. As far as I
know the fpdoc is sensitive to which platform it is running on (unless
explicitly told otherwise), and will
Hi,
https://www.freepascal.org/docs-html/rtl/sysutils/longrec.html
I'm referring to the documentation shown in the URL above. As far as I
know the fpdoc is sensitive to which platform it is running on (unless
explicitly told otherwise), and will generate documentation according to
that platform.
Kevin Lyda schrieb am Mi., 8. Mai 2019, 10:58:
> Amazingly I still have a number of my high school computer science
> projects which were written in Turbo Pascal 3. And a few are almost
> not horribly embarrassing.
>
> I'd like to port them to fpc and write up the experience but I know
> what
Amazingly I still have a number of my high school computer science
projects which were written in Turbo Pascal 3. And a few are almost
not horribly embarrassing.
I'd like to port them to fpc and write up the experience but I know
what the huge issue is: it uses the graphics.bin library which was
Op 5/7/2019 om 11:14 AM schreef Sven Barth via fpc-pascal:
It depends whether the musl libc also leads to the inclusion of
"libc.so.6" in the ELF files. If yes, then all should be good (except
if not all calls are available, but then recompilation wouldn't help
either), if not everything
13 matches
Mail list logo
