Hi,

2011/5/19 Ladislav Lacina <[email protected]>:
>
> Yes, I like the FPC 1.0.10. The IDE is a little bit unstable and there are 
> bugs in Ansistrings and sometimes failing type control but all important 
> components work.

Well, Marcov is a bit less tolerant of it than you (inline asm and
calling convention bugs??).

> In 2.x.x versions were some major DOS related bugs fixed

Right, I know that 2.2.0 wasn't very usable, but since then everything
has been more or less okay (from what little I've tested and heard).

> but there still is one very severe. Look at my bugreport.
> http://bugs.freepascal.org/view.php?id=18113

Yes, I remember you mentioning that, and also you said the devs
weren't very helpful. Here's what I take issue with (and I've heard
this before too):

"It fixed the test I created. Apparently it's something different
then, and I cannot fix it since I don't have a platform that can run
go32v2 binaries."

Uh, hello, VirtualBox + FreeDOS, DOSEMU + FreeDOS, native FreeDOS,
WinXP, OS/2, DOSBox even ... he has literally no excuse other than too
busy, too lazy, too dumb, etc. (I'm not trying to pick on him, but
it's just ridiculous.)

Perhaps he's on Linux x86-64 and really thinks that DOSEMU doesn't
work there (seems to be a common misconception). In any case, I
suggest you ask him what platform he uses and tell him there's no
dearth of DOS compatibility!

> Except that still does not well work debugging programs running in graphics 
> mode. More preciously:
> Everything works except saving content of graphics screen:
> Program runs until breakpoint - then is stopped and screen is switched into 
> FPC IDE. After work in IDE you select "Continue in running program", graphics 
> mode is restored but not the screen content. Screen is black.

I suggest you isolate the problematic code in a separate unit (if
possible) and compile it independently without any optimizations
(assuming that would work okay).

P.S. Keep in mind that nobody has stepped up to be official FPC DOS
maintainer either, so it's been "coasting" for a looooong time.   :-(

------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its 
next-generation tools to help Windows* and Linux* C/C++ and Fortran 
developers boost performance applications - including clusters. 
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Freedos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Reply via email to