Following a couple of questions on how to deal with them and to clarify the previous post on code container.
Forté use them to store development definition as opposed to the .c, .cpp, .cxx, .h or .java files. This is handled by the Forté IDE/Runtime.
They are also used to save runtime information when an application is being deployed in interpreted mode, using the Forté IDe it is still possible
The way Forté 4GL reads and write to them is not relevant as long as we can use Forté runtime to extract what's in it. So there is very little incentive in trying to attack those files from a Java environment, Forté does it very well and can feed Java with useful information that can be hard to extract directly or from an export.
1 comment:
Excellent posts! I am always curious to know what happened to the product. While searching, I stumbled on your site. I am happy to find a blog about Forte!! Do you still work in it?
It feels very nostalgic to read your posts. I developed using Forte between 1999 - 2003. I loved the product and IMHO it was way better than J2EE in the distributed world. Was sorry to see it go.
I now work in Powerbuilder(PB). Seems like several products swiped ideas from Forte World. PB + EA Server is very much like Forte UDS.
Cheers
Sam V
Post a Comment