> >On Mon, 22 Aug 2005, Lowell C. Savage wrote:
> > > the way to go.
> >
> >It will still cause problems, because the C library also will interfere
> >with the
> >Video and CRT units...
> >
> >It's planned to base the CRT unit on the video unit (so they would work
> >together),
> >but until now n
At 21:45 22/08/2005, you wrote:
On Mon, 22 Aug 2005, Lowell C. Savage wrote:
>
> Some, perhapsI ran into this problem when I was still compiling the
> program as a pure Pascal program. (I had the interfaces to other languages
> commented out.)
>
> I'm using: CRT, IO, DOS, Video, Printer,
On Mon, 22 Aug 2005, Lowell C. Savage wrote:
>
> Some, perhapsI ran into this problem when I was still compiling the
> program as a pure Pascal program. (I had the interfaces to other languages
> commented out.)
>
> I'm using: CRT, IO, DOS, Video, Printer, Graph, and Drivers.
This is t
Type checking of compile time expression has been added to Free Pascal
Compile time expression are used in $IF/$IFC, and under mode MacPas, in
$SETC
This should hopefully help everyone to find some errors, but if it makes
trouble for anyone please let me know.
---
Implementation details:
E
"Tomas Hajny" wrote, in part:
> I'm running an old DOS (originally compiled with TP) Pascal program that
> uses the CRT unit. It has several places where it uses KeyPressed/ReadKey
> to pause a screen until the user responds. It uses the same combination
> to
> read user input. However, it ap
On 21-08-05 15.49, Søren Ager wrote:
Any ideas why?
Changing:
DOMString = WideString;
DOMPChar = PWideChar;
to:
DOMString = String;
DOMPChar = PChar;
in dom.pp fixed the problem. So I guess the WideString is broken in fpc
for OS/2. Is there anyway to disable it so I don't run into
>Most programmers today
>see some API or platform as their working base, which is IMHO like
>standing on a cloud - they don't see the transistors etc. Would they
>be capable to build a computer from scratch? A mechanical cash register?
>A hydraulic-based computer?
>
> But you can't make money with
> I know nothing about the first program, executed by the first computer,
> if that's what you are asking, but I guess it was probably written by
> hand in machine language.
>
That leads to the "first program that ran the first software program" actually
being a hardware program. The
transistors
L505 wrote:
>>I know nothing about the first program, executed by the first computer,
>>if that's what you are asking, but I guess it was probably written by
>>hand in machine language.
>>
>
>
> That leads to the "first program that ran the first software program"
> actually being a hardware pr
On 21-08-05 15.49, Søren Ager wrote:
Any ideas why?
If it's any help here is teh contents of popuplog.os2:
08-21-2005 15:44:56 SYS3175 PID 01d0 TID 0001 Slot 006f
D:\SOURCE\ABRG\XMLTEST.EXE
c005
P1=0001 P2= P3= P4=
EAX=200602f4 EBX=
Am Montag, den 22.08.2005, 14:12 +0200 schrieb Anton Tichawa:
> Marc Santhoff wrote:
>
> >Am Sonntag, den 21.08.2005, 16:19 -0700 schrieb L505:
> >
> >
> >>>The first compilers were written in assembly language. This allowed
> >>>
> >>>
> >>for
> >>
> >>
> >>>the next generation compil
Marc Santhoff wrote:
Am Sonntag, den 21.08.2005, 16:19 -0700 schrieb L505:
The first compilers were written in assembly language. This allowed
for
the next generation compilers to be written in a high level language.
And the assembly language was just magically inserted
Am Sonntag, den 21.08.2005, 16:19 -0700 schrieb L505:
> > The first compilers were written in assembly language. This allowed
> for
> > the next generation compilers to be written in a high level language.
>
>
> And the assembly language was just magically inserted into the memory
> with that mag
13 matches
Mail list logo
