Hi,

I am currently migrating a project from Delphi for Win32 to Delphi.net.

Part of my code currently goes into a directory and pulls out a random file from this directory and loads the contents of the file for me.  This code doesn't seem to work in Delphi.Net.  It uses PString and a number of functions in SysUtils that don't seem to be present in Delphi.net's SysUtils file.

If anyone can help me please, it would be greatly appreciated!

Many thanks,

Jonathan Mackey

Jonathan Mackey a écrit :

> I am currently migrating a project from Delphi for Win32 to
> Delphi.net.

Delphi Prism is not he same as Delphi.NET; there are differences in 
language which may cause problems.

> Part of my code currently goes into a directory and pulls out a
> random file from this directory and loads the contents of the file
> for me.  This code doesn't seem to work in Delphi.Net.  It uses
> PString and a number of functions in SysUtils that don't seem to be
> present in Delphi.net's SysUtils file.

That is because you are trying to translate Delphi for Win32 to Delphi 
Prims, not Delphi.NET. The libraries that Delphi.NET used (VCL, etc) are 
not available in the Prism world.

Types like PString are considered "unsafe" and will need to be replaced 
with a managed type.

Joanna

-- 
Joanna Carter [TeamB|http://www.teamb.com]
Consultant Software Engineer

Jonathan Mackey wrote:

> Hi,
> 
> I am currently migrating a project from Delphi for Win32 to
> Delphi.net.
> 
> Part of my code currently goes into a directory and pulls out a
> random file from this directory and loads the contents of the file
> for me.  This code doesn't seem to work in Delphi.Net.  It uses
> PString and a number of functions in SysUtils that don't seem to be
> present in Delphi.net's SysUtils file.
> 
> If anyone can help me please, it would be greatly appreciated!

Like Joanna said, you seem to be confusing Delphi for .NET, which came
with Delphi 8, Delphi 2005, 2006 and 2007, and Delphi Prism, which is a
different language (although quite similar) and does not use the Delphi
runtime library or VCL for .NET.

http://prismwiki.codegear.com/en/ShineOn

There is an effort to mimic some of the Delphi runtime library units,
called ShineOn, which may be of some help, but you'll still have to get
rid of PString and other pointer tricks.

http://prismwiki.codegear.com/en/ShineOn

Why don't you post your Delphi code to .attachments so people can take
a look at it?

FWIW, if you are actually really using Delphi for .NET, you should post
to embarcadero.public.delphi.language.delphi.dotnet instead.

-- 
Rudy Velthuis (TeamB)        http://www.teamb.com

"Argue for your limitations, and sure enough they're yours."
 -- Richard Bach

Rudy,

> http://prismwiki.codegear.com/en/ShineOn
> 
> There is an effort to mimic some of the Delphi runtime library units,
> called ShineOn, which may be of some help, but you'll still have to get
> rid of PString and other pointer tricks.

I had a look at it. There is still a lot of stuff missing.
Maybe it could be an idea to use some function of the deprecated rtl.net 
as a template.

BTW I tried to contact you. Please have a look at your private messages.

-- 
Roman

Roman Kaßebaum wrote:

> Rudy,
> 
> > http://prismwiki.codegear.com/en/ShineOn
> > 
> > There is an effort to mimic some of the Delphi runtime library
> > units, called ShineOn, which may be of some help, but you'll still
> > have to get rid of PString and other pointer tricks.
> 
> I had a look at it. There is still a lot of stuff missing.

Sure. AFAIK it is an open source effort.

> Maybe it could be an idea to use some function of the deprecated
> rtl.net as a template.
> 
> BTW I tried to contact you. Please have a look at your private
> messages.

OK.


-- 
Rudy Velthuis (TeamB)        http://www.teamb.com

"It is the job of thinking people not to be on the side of the
 executioners." -- Albert Camus

Rudy Velthuis (TeamB) schrieb:

> Sure. AFAIK it is an open source effort.

Oh, I thought that Embarcadero and RemObjects are pushing it.

-- 
Roman

> {quote:title=Rudy Velthuis (TeamB) wrote:}{quote}
> 
> There is an effort to mimic some of the Delphi runtime library units,
> called ShineOn, which may be of some help, but you'll still have to get
> rid of PString and other pointer tricks.
> 
> http://prismwiki.codegear.com/en/ShineOn
> 

I wasn't having any luck downloading ShineOn from 

http://code.remobjects.com/p/shineon/

The code at the old repository

http://public.svn.remobjects.com/trunk/PUBLIC/Prism/ShineOn/Source/

Seems to be a bit older (using NUnit 2.4.5 from Nov 24 2007 instead of the current 2.5.2).  

For the record I am able to obtain the source for other projects from http://code.remobjects.com/ just fine.

--
-Jim McKeeth
www.Delphi.org
www.DavinciUnltd.com

Roman Kaßebaum wrote:

> Rudy Velthuis (TeamB) schrieb:
> 
> > Sure. AFAIK it is an open source effort.
> 
> Oh, I thought that Embarcadero and RemObjects are pushing it.

RemObjects started it, but AFAIK, everyone can take part.

-- 
Rudy Velthuis (TeamB)        http://www.teamb.com

"We don't make mistakes, we just have happy little accidents."
-- Bob Ross, "The Joy of Painting"

Jim McKeeth wrote:

> I wasn't having any luck downloading ShineOn from 
> 
> http://code.remobjects.com/p/shineon/
> 
> The code at the old repository
> 
> http://public.svn.remobjects.com/trunk/PUBLIC/Prism/ShineOn/Source/
> 
> Seems to be a bit older (using NUnit 2.4.5 from Nov 24 2007 instead
> of the current 2.5.2).
> 
> For the record I am able to obtain the source for other projects from
> http://code.remobjects.com/ just fine.

I haven't done anything with ShineOn for a while, so I can't tell you
anything more about it, sorry.

-- 
Rudy Velthuis (TeamB)        http://www.teamb.com

"Lohr's Law: The future is merely the past with a twist — and 
 better tools." -- Steve Lohr

Hi,

Just to let you guys know... I kinda cheated!

I packaged up the unsafe code into a dll, and I reference it from my .net application! :)

It works now!  Untidy fix, but I'm on a deadline!

Thanks!

Jonathan

Rudy Velthuis (TeamB) schrieb:

> RemObjects started it, but AFAIK, everyone can take part.

Theoretically yes, but I haven't got Prism.

-- 
Roman

Roman Kaßebaum wrote:

> Rudy Velthuis (TeamB) schrieb:
> 
> > RemObjects started it, but AFAIK, everyone can take part.
> 
> Theoretically yes, but I haven't got Prism.

Ah, yes, that might slow down things a bit. <g>

-- 
Rudy Velthuis (TeamB)        http://www.teamb.com

"Perl is another example of filling a tiny, short-term need, and
 then being a real problem in the longer term." -- Alan Kay

Rudy Velthuis (TeamB) schrieb:

> Ah, yes, that might slow down things a bit. <g>

LOL.

-- 
Roman

> {quote:title=Roman Kaßebaum wrote:}{quote}
> Rudy Velthuis (TeamB) schrieb:
> 
> > Sure. AFAIK it is an open source effort.
> 
> Oh, I thought that Embarcadero and RemObjects are pushing it.
> 
> -- 
> Roman

Avoid ShineOn. It looks completely moribund. I spent a lot of time last spring posting patches and bug reports, all of which were ignored.

http://code.remobjects.com/p/shineon/issues/

ShineOn may be open-source in some sense, but there's nobody home there.

Better just bite the bullet and rewrite all code completely so you don't need a Delphi-like RTL.

Thanks.

-Phil

Hi Phil,

> Avoid ShineOn. It looks completely moribund. I spent a lot of time last spring posting patches and bug reports, all of which were ignored.
> 
> http://code.remobjects.com/p/shineon/issues/
> 
> ShineOn may be open-source in some sense, but there's nobody home there.


I have the same impression.


> Better just bite the bullet and rewrite all code completely so you don't need a Delphi-like RTL.


I don't like to say it directly but one should think a short moment 
about the programming language.

BTW, you should send me your sf login.

-- 
Roman

> {quote:title=Roman Kaßebaum wrote:}
> I don't like to say it directly but one should think a short moment 
> about the programming language.
> 

Prism is a good choice as long as you're completely comfortable with this statement:

"Prism's Pascal is not the same as Delphi's Pascal, Prism's RTL is not the same as Delphi's RTL, and Prism's forms are not the same as Delphi's forms."

One way to preserve existing Delphi non-UI code is to put it in a native DLL and call it from a Prism assembly. That presents cross-platform possibilities too:

http://wiki.lazarus.freepascal.org/Using_Pascal_Libraries_with_.NET_and_Mono

You can also put Delphi forms in a DLL and use them from .NET assemblies too. They may look just a bit different from .NET forms, but it can save a huge amount of pointless rewriting (only a tyro would immediately start rewriting perfectly good code)..

I write GIS plug-ins. The particular GIS used only supports .NET plugins. I had written a big plugin in VB.NET and thought I would give Prism a shot for the next plugin I write. Prism worked fine. And to avoid rewriting about 6,000 lines of code and several complex forms that used Orph TOvcTable controls, I just put those units into a DLL. Took about one day of work to decide how to pass info to the DLL and get info back. The forms in the native DLL work great with my Prism plugin assembly and you really 
can't tell unless you're really looking that the forms are not .NET forms.

Also, if you don't yet have Prism, just install the free command line Prism compiler. It works fine on Macs too.

Thanks.

-Phil