Re: Euphoria 2.0

new topic     » goto parent     » topic index » view thread      » older message » newer message

David Cuny wrote:
> I took a look at it, and decided to wait until I got my hands on a version
> that supported more than 300 lines... It's too darned hard to write code
> without a decent debugger, and the code to generate a basic window takes
> about 250 lines.

Debugging a .exw program using trace is awesome compared to doing it in
dos.  The debugger sits nicely in the dos window and the real windows
crap can do its thing in its own separate window.  I also use the
console window to display variables in the WndProc function so I can see
what's going on in there.
---- code inside WndProc function in window.exw ----
printf(1, "WndProc: hwnd=%d iMsg=%d wParam=%d lParam=%d\n",
{hwnd,iMsg,wParam,lParam})
---- code ends ----

Thanks to JesusC for the win32 links in private mail, here they are in
case anyone else is interested:
> from Borland site:
>
> <ftp://ftp.borland.com/pub/techinfo/techdocs/language/delphi/gen/win32.zip>
> I'ts some 10 Mb size...
>
> <http://www-uk.hpl.hp.com/people/slo/windows/win32faq.html>
>

The first url is the big help file that has a lot of info about how to
program using the win32 dlls but not how to link to them.  I found a
_big_ VB include file that has a lot of variable, function and structure
declarations, that could probably be converted to Euhporia without too
much trouble (or not smile.  I wrote a quick Euphoria program to convert
it automatically but I haven't had time to test it.  (I made output file
of just the GDI routines that exw.exe accepted as syntactically correct,
with only a few minor touch-ups)  If anyone's interested just drop me a
line.

> -- David Cuny
>
> BTW: I'm still working on reconciling Pete's SVGA code into the the EE editor.
>      I had promised some people that it would be released this week, but it
>      looks like I'm going to slip another week. Sorry. I've got everything but
>      the EE file reconciled.

While you're at it, please add some sort of detection for .exw files so
that exw.exe gets called instead of ex.exe and we don't get the "this
program must be run using exw blah blah..." message.  As for SVGA
routines, I don't actually use them for real editing.  They're just too
slow compared to text mode.  The graphic gizmos are neat, but I prefer
speed more than anything.

Happy Coding!
--
                   _____         _____        _____
    ________      /\    \       /\    \      /\    \
   /   \    \    /  \____\     /  \____\    /  \____\
  /  _  \____\  /   / ___/_   /   /____/   /   / ___/_
 /  / \  |___| /   / /\____\ /    \    \  /   / /\____\
 \  \_/ /    / \   \/ / ___/_\     \    \ \   \/ / ___/_
  \    /____/   \    / /\    \\/\   \    \ \    / /\    \
   \   \    \    \   \/  \____\  \   \    \ \   \/  \____\
    \   \    \    \      /    /   \   \____\ \      /    /
     \   \____\    \    /    /     \  /    /  \    /    /
      \  /    /     \  /    /       \/____/    \  /    /
       \/____/       \/____/xseal at harborside.com\/____/

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu