In article <brvelu$1umc$1@digitaldaemon.com>, Ilya Minkov wrote:
>>>My biggest headache is learning how librarys, headers, an such, all fit together
> 
> Lewis, you don't need to learn C++, but i would recommend you to get LCC-Win32 compiler and get some exposure to C. This will give you some knowledge of compilation model, idiotic syntax parts which are preserved in D, and so on. Something of the culture which (sadly) is compulsory for every modern programmer. While the compiler is not necessarily good for production work (debugger is weakish, no C++, ...), it has a neat and simple IDE, and - most importantly - a nice tutorial book. All is for free. The book gives you some simple and Windows programming, but doesn't take too far into the depths of C language and standard libary which you won't need later. So, go though the tutorials, and then switch happily back to D. You will really feel a great relief. After you're comfortable with D, you might want to learn some C++ and come back to D with relief and so on... ;)
> 
> In fact, i would like to recommend some book doing the same with a simple subset of C++ and STL, but i'm aware of none. Anyway, Bjarne Stroustrup has been considering modern C++ as a better language for beginners than C.

They say that Accelerated C++ (Koenig & Moo 2000, http://www.acceleratedcpp.com/) is a really good book. I've only shortly browsed through it myself, but you check out for example Francis Glassborow's review for more praise.  (Link can be found from the book's web site.)

In short, the book is supposed to introduce the most useful C++ concepts without overwhelming the beginner with details inherited from C.

-Antti

"Mark T" <Mark_member@pathlink.com> wrote in message
news:bs9mls$1as2$1@digitaldaemon.com...
|
| So you build the GUI using Delphi and then use your library DLL to
interface
| them?  Maybe you could put a more complete step by step example on your
web
| site.
|
| I've done similar things with VB and C for quick and dirty apps. Use the
GUI
| building tool for the user interface part and do the all the rest in a
more
| portable language (and one that I know). It was a lot quicker than doing
MFC. It
| also forces you to decouple the user interface layer from the domain layer
which
| is a good design practice.
|
| Mark
|
|

Not really. Let me show by example.
In Delphi you define windows by inheriting from TForm. What I'm doing is
defining a TForm in D, which has a reference to a Delphi TForm. So, if you
do this in D:
class MyForm : TForm { ... }
...
(new MyForm).ShowModal();
In the constructor of TForm, there's a call to initialize a new TForm from
Delphi, and save it in a void *. Calls like ShowModal are then passed to
this member, which is a Delphi object.
I'm not good at explaining. I've uploaded what I've done so far (not
much, btw) so you can judge by yourself. Especially, I'd like to hear
comments about the way events are handled. I've also set up
http://s3.invisionfree.com/ln5yrestgv/index.php?act=idx, a forum to discuss
about anything D related, including Delphi4D. You have to register to access
it, but I'm gonna try to change that. Anyway, express yourself there.

-----------------------
Carlos Santander Bernal

"Carlos Santander B." <carlos8294@msn.com> wrote in message
news:bsn69m$23p9$1@digitaldaemon.com...
| comments about the way events are handled. I've also set up
| http://s3.invisionfree.com/ln5yrestgv/index.php?act=idx, a forum to
discuss
| about anything D related, including Delphi4D. You have to register to
access
| it, but I'm gonna try to change that. Anyway, express yourself there.
|

Ok, no need to register to read, but if you want to post, you need to set up an account.

-----------------------
Carlos Santander Bernal