In our previous episode, Tomas Hajny said:
> Have you checked it in fixes or trunk? In any case, I've tried it directly
> with the 2.6.2 binary before posting - even if I pass -Xi explicitly, the
> compiler still complains about go32v2-ld.exe not found if it is not
> accessible (and linking fails).
On 18/09/2013 16:19, Bart wrote:
> RomanToInt acceps rather ludicrous values:
>
> RomanToInt('MDCLXVIVXLDM') = 2209
> RomanToInt('M') = 1002 //calculated as 3 + (1000-1)
>
> Both examples represent invalid roman numbers by any standard.
> Also I do not think Roman numerals can be negative...
Am 20.09.2013 09:20, schrieb Marco van de Voort:
In our previous episode, Tomas Hajny said:
Have you checked it in fixes or trunk? In any case, I've tried it directly
with the 2.6.2 binary before posting - even if I pass -Xi explicitly, the
compiler still complains about go32v2-ld.exe not found
Am 19.09.2013 22:46, schrieb Tomas Hajny:
On Thu, September 19, 2013 21:55, Sven Barth wrote:
On 19.09.2013 17:28, Tomas Hajny wrote:
.
.
2) You still need at least a linker for the GO32v2 target (FPC internal
linker does not support this target) and that is the somewhat tricky
part.
Hmm?
In our previous episode, Sven Barth said:
> >
> > I'm not sure how far along it is, and if it is default. (is the internal
> > linker always default if available?)
> Yes, the internal linker is used by default. See options.pas, line 3246:
>From the code and looking at the i_ records, I'd say that
Hi list,
Recent posts have lead me to look again at my FPC/Lazarus
downloader/compiler fpcup [1] to see if I could get cross compiling
going from win64 or win64 to Go32v2.
This works for me:
1) Setup:
Create directory c:\development
Get crosscompile binutils from
ftp://ftp.freepascal.org/pub/fpc/
On 9/20/13, Bart wrote:
> Any invalid char in S will result in Result being 0;
> So doc is wrong about that.
Reported that in bugtracker: http://bugs.freepascal.org/view.php?id=25061
Bart
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
htt
On 9/20/13, wkitt...@windstream.net wrote:
>
> a[n] := #255; // works
> a[n] := $ff; // does not work
>
> ideally, there would be multiple bytes...
>
> a[n] := $C2AD or a[n] := $C2$AD
>
Not sure what you want:
a[n] := #$FF; (which equals a[n] := #255)
a[n] := '$FF' (note the single quot
On 9/20/13, Reinier Olislagers wrote:
> 1. I'll respond with the expected answer: "What does Delphi do" (if it
> has this function?
D7 PE does not have it.
> 2. I wouldn't be bothered by negative numbers... even the Romans used to
> have negative posessions (= debts) and they didn't have double
On 20/09/2013 18:33, Bart wrote:
> On 9/20/13, Reinier Olislagers wrote:
>> 2. I wouldn't be bothered by negative numbers... even the Romans used to
>> have negative posessions (= debts) and they didn't have double entry
>> bookkeeping yet ;) Also, the documentation [1] mentions it as a feature.
>
On Fri, September 20, 2013 18:42, Reinier Olislagers wrote:
Hi Reinier,
> Recent posts have lead me to look again at my FPC/Lazarus
> downloader/compiler fpcup [1] to see if I could get cross compiling
> going from win64 or win64 to Go32v2.
>
> This works for me:
> 1) Setup:
> Create directory c
i have a static array of strings that i need to fill as hex bytes... i can do
this in decimal but it would be easier to convert other data if i can do it in
hex since the data is represented in hex...
a[n] := #255; // works
a[n] := $ff; // does not work
ideally, there would be multiple byt
And please, before anyone gets offended by my postings in this thread:
- I just stubled on this whils doing a kind WTF implementation of
something like this (and at that time I didn't even knew we had
StrUtils.RomanToInt).
- I don't think it is the end of the world just because the StrUtils
versio
On 9/20/13, Reinier Olislagers wrote:
> 2. The other cases you mentioned in your OP are bugs, not features.
Unless the Greek do the same, someone with recent Delphi should test.
If that's the case we're doomed to follw that.
Bart
___
fpc-pascal mailli
On 9/20/13, Reinier Olislagers wrote:
> The question however becomes "what is the
> algorithm for deciding invalid characters" which IMO will become a mess
> very quickly. Much better to just consider the entire input as invalid.
>
Here's my implementation:
program test;
{$mode objfpc}
{$H+}
On 20/09/2013 18:55, Tomas Hajny wrote:
> On Fri, September 20, 2013 18:42, Reinier Olislagers wrote:
> Which FPC branch do you use, trunk or fixes? If it is trunk, it should be
> able to use not only the internal assembler but also internal linker and
> thus these binutils are not used at all (unl
In our previous episode, Reinier Olislagers said:
> > able to use not only the internal assembler but also internal linker and
> > thus these binutils are not used at all (unless also using -Xe).
>
> Hi Tomas,
> Thanks a lot!
>
> I've tested it with trunk. I've adapted fpcup to not error out if
On Fri, September 20, 2013 21:30, Marco van de Voort wrote:
> In our previous episode, Reinier Olislagers said:
>> > able to use not only the internal assembler but also internal linker
>> and
>> > thus these binutils are not used at all (unless also using -Xe).
>>
>> Hi Tomas,
>> Thanks a lot!
>>
18 matches
Mail list logo
