>And the same machine otherwise ?
Yes everything is the same other than the version I am trying to compile
with, and being run on the same system.
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/l
Op 20-12-2024 om 15:36 schreef James Richters:
I assume that it is exactly the same source on exactly the same system with
exactly the same compiler configuration.
And the same machine otherwise ?
___
fpc-pascal maillist - fpc-pascal@lists.free
James Richters via fpc-pascal schrieb am
Fr., 20. Dez. 2024, 15:16:
> It does seem that '?' is being substituted in, but I don't know why, the
> ascii codes I am using are valid character they are:
> #$D0 - #$EF which are these: Þßàáâãäåæçèéêëìíîïï It's not like they are
> non-characters like e
>Could it be due to a change of compilation mode (DELPHIUNICODE etc.) by the
user?
I haven't change any code at all but the unit that does the TProcess call is
being compiled with:
{$Mode TP}{$I-}
{$modeswitch exceptions}
{$R+}
James
___
fpc-pascal mai
I just tried compiling with the march version with -CpCOREI -OpCOREI -CfAVX2
-dMT and it worked as expected... so it's not the processor change that
caused the issue.
James
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
https://lists.freep
>I assume that it is exactly the same source on exactly the same system with
exactly the same compiler configuration.
Well... you would think I would be compiling it the same way, but I'm not...
I thought I was be when I went to verify that I found that I did make a
change.
I was compiling with:
It does seem that '?' is being substituted in, but I don't know why, the
ascii codes I am using are valid character they are:
#$D0 - #$EF which are these: Þßàáâãäåæçèéêëìíîïï It's not like they are
non-characters like escape or something.
They are valid ascii characters. I went to the character m
Op 20-12-2024 om 14:44 schreef Tomas Hajny via fpc-pascal:
I am not aware of any such changes, but given your remark about the
meaning
of 3F, the latter seems a likely explanation.
Could it be due to a change of compilation mode (DELPHIUNICODE etc.)
by the user?
I assume that it is exac
On 2024-12-20 14:22, Michael Van Canneyt via fpc-pascal wrote:
On Fri, 20 Dec 2024, Karoly Balogh via fpc-pascal wrote:
Hi,
On Fri, 20 Dec 2024, Michael Van Canneyt via fpc-pascal wrote:
If I compile it with:
Free Pascal Compiler version 3.3.1-16969-g798f2ba632-dirty
[2024/11/28] for
i386
I
On Fri, 20 Dec 2024, Karoly Balogh via fpc-pascal wrote:
Hi,
On Fri, 20 Dec 2024, Michael Van Canneyt via fpc-pascal wrote:
If I compile it with:
Free Pascal Compiler version 3.3.1-16969-g798f2ba632-dirty [2024/11/28] for
i386
I get almost what I expected, but my #$EE is now been changed t
Hi,
On Fri, 20 Dec 2024, Michael Van Canneyt via fpc-pascal wrote:
> > If I compile it with:
> > Free Pascal Compiler version 3.3.1-16969-g798f2ba632-dirty [2024/11/28] for
> > i386
> > I get almost what I expected, but my #$EE is now been changed to #$3F (and
> > all similar codes in the range
On Thu, 19 Dec 2024, James Richters via fpc-pascal wrote:
I am using ProgProcess to execute a program with data passed as parameters.
I'm adding the parameters with this:
ProgProcess := TProcess.Create(nil);
ProgProcess.Executable := 'cmd.exe';
ProgProcess.Parameters.
12 matches
Mail list logo