I have seen this question in here, and the usual answer is that you only
want to go the .DLL route if you have a lot of processor-specific code doing
complex functions(?) that need to be put in as native code, and even then
the gains are only modest at best. I haven't done the .DLL compilation for
our project, however, so I don't know for sure.
There is a document:
PowerBuilder 5.0 Compiled Code White Paper
http://techinfo.sybase.com/css/techinfo.nsf/DocId/ID=44527
Read this for more information!
Peter Szintai
In article <qpDOUKbk#GA....@forums.sybase.com>,
"alexander" <alexan...@knight-hub.com> wrote:
>
> All that I could learn from the books about PBDs and DLLs is that a machine
code
> executable is larger than a PowerBuilder code executable, but
> will run faster. What other factors are important to consider when you decide
> which of the two you want to use? What really happens, if to look at it from a
> technical angle?
>
-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
I personally felt (and verified by various posts) that pcode is faster considering
general application preformace. Machine code is faster when it comes to computations
as in mathematical, string manipulations etc.
Hope this helps
Anil
Considering that the primary bottleneck in a poor performing system is the
data access (retrieval and update), DLLs wouldn't be much help there.
Personally speaking, compiling to machine code has always been more of a
PITA than it's been worth, so we stuck to PBDs and haven't regretted it...
Paul Horan
VCI
Springfield, MA
alexander <alexan...@knight-hub.com> wrote in message
news:qpDOUKbk#GA....@forums.sybase.com...
Factors:
1) It won't run faster unless your application does a lot of computation.
Typical operations like data access are actually faster in Pcode.
2) Machine code exe's take much more time to create
3) Machine code exe's are less stable than pcode
--
Regards,
Millard[TeamPS]
Power3, LLC - Customized Training