Re: Pseudo Code or Compiled

In article <4kavsi$bpn@newsgate.dircon.co.uk>, Terry Boyland <windata@dircon.co.uk> writes > >I have been having an argument with a third party software house >( bit of a waste of time really ! ) > >We have been shipped an application which has been compiled to pseudo code >and a runner. I know that the pseudo code is loaded in memory each time >a user calls that program so that 6 users using the same program load the >code into the data area of the stack 6 times taking up large amounts of >memory whereas compiled code can be shared in memory meaning that it will >load only once into the text area of the stack and will be shared by the >other five. This has a potential to give large memory savings. > >The supplier says this is all crap and that there is no business case for >compiling the code > >Am I missing some thing here or are they just not prepared to spend any >money again ?? There were two excellent replies giving information about the performance impact of compilled & p-code solutions. However one bit of information Terry doesn't give is how many places/platforms they are shipping to. Once it is more than one place, shipping compilled 4GL starts to become a nightmare as you need access to a binary-compatable for *each* platform you are releasing, which rapidly turns into a nightmare! -- Sally Woolrich