Re: [ql-users] Turbo Compiled Programs - Parameter passing
On Wed, 19 Feb 2003 17:29:18 EST, [EMAIL PROTECTED] wrote: snip The other quirk is that Turbo will report an error if you pass a different type of variable to the parameter type listed in the reference, for example: I don't believe that is a bug per se. You have to take into account that the implicit datatypes that are used are there to create faster code. So if you IMPLICITLY define a datatype to use and you feed it something else then it SHOULD complaine If you therefore 'trick' Turbo, it should not only report an error but get a hammer out of the screen and break your QL :-) -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
Re: [ql-users] Turbo Compiled Programs - Parameter passing
In a message dated 19/02/2003 23:19:29 GMT Standard Time, [EMAIL PROTECTED] writes: I don't believe that is a bug per se. You have to take into account that the implicit datatypes that are used are there to create faster code. So if you IMPLICITLY define a datatype to use and you feed it something else then it SHOULD complaine If you therefore 'trick' Turbo, it should not only report an error but get a hammer out of the screen and break your QL :-) Possibly so, but it is the incompatabilities with S*BASIC such as these, which make Turbo such a steep learning curve, even for someone who used it as my only compiler some 5/6 years ago... -- Rich Mellor RWAP Software 35 Chantry Croft, Kinsley, Pontefract, West Yorkshire, WF9 5JH TEL: 01977 610509 http://hometown.aol.co.uk/rwapsoftware
Re: [ql-users] Turbo Compiled Programs - Parameter passing
On Wed, 19 Feb 2003 18:23:50 EST, [EMAIL PROTECTED] wrote: In a message dated 19/02/2003 23:19:29 GMT Standard Time, [EMAIL PROTECTED] writes: I don't believe that is a bug per se. You have to take into account that the implicit datatypes that are used are there to create faster code. So if you IMPLICITLY define a datatype to use and you feed it something else then it SHOULD complaine If you therefore 'trick' Turbo, it should not only report an error but get a hammer out of the screen and break your QL :-) Possibly so, but it is the incompatabilities with S*BASIC such as these, which make Turbo such a steep learning curve, even for someone who used it as my only compiler some 5/6 years ago... It's a point of view I guess... When you write with intent to compile some things need to be taken into account... You would never assume the same though for VisualBasic though would you? (Okay bad example ;-) Phoebus -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
Re: [ql-users] Turbo Compiled Programs - Parameter passing
In a message dated 19/02/2003 23:46:08 GMT Standard Time, [EMAIL PROTECTED] writes: It's a point of view I guess... When you write with intent to compile some things need to be taken into account... You would never assume the same though for VisualBasic though would you? (Okay bad example ;-) Definitely a bad example - got nothing on S*BASIC -- Rich Mellor RWAP Software 35 Chantry Croft, Kinsley, Pontefract, West Yorkshire, WF9 5JH TEL: 01977 610509 http://hometown.aol.co.uk/rwapsoftware
Re: [ql-users] Turbo Compiled programs
In a message dated 02/11/02 15:13:04 GMT Standard Time, [EMAIL PROTECTED] writes: George Gwilt is the expert on how to get at the source of compiled programs. However it may not be possible unless the program has been compiled with flags in the same way as C programs can be compiled with a switch so that a debugger can access the lines and enable one to step through it. I know he uses a similar switch for debugging Turbo itself. John may think I know more than I, in fact do. It is true that I will find ways of stepping through a Turbo compiled program to find what is happening. That is not at all the same thing as un-compiling a program. The only way I would embark on such a project is if it were absolutely the only way that I could see to achieve something that I thought was ABSOLUTELY ESSENTIAL. In that case I would probably find a solution. As it is . . . . George
Re: [ql-users] Turbo Compiled Programs
[EMAIL PROTECTED] wrote: However, many of the early commercial programs have been compiled with either Turbo or QLiberator. Is there any way of writing a program which will generate the source code for compiled programs?? As far as I know Qliberated programs are mostly just tokenized versions of the originals. The tokens are interpreted by the runtime library. Due to this fact it should theoretically be possible to get some sort of source output out of compiled versions. But as probably nobody knows the token format anymore you can as well forget it. It'd probably be less work to re-write those programs than to write a decompiler. Marcel
Re: [ql-users] Turbo Compiled Programs
- Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, October 29, 2002 9:13 PM Subject: Re: [ql-users] Turbo Compiled Programs In a message dated 29/10/02 18:57:21 GMT Standard Time, [EMAIL PROTECTED] writes: I used to play cribbage when I had an idle moment(Library GG 02 but I have been unable to play since using QPC.Is it possible to get it working?.Arnie Hi Rich here are the files in question.They will work on a standard QL but on QPC it loads up and stops at the commence ment of play. It does not seem much wrong(famous last words) arnie CRIB_BOOT Description: Binary data CRIB Description: Binary data
Re: [ql-users] Turbo Compiled Programs
At 05:37 ìì 31/10/2002, Arnold Clarke wrote: That may also be the problem when you're transferring the file to your PC I tend to forget about that limitation and always end up with files that do not work... The best sequence is: 1. Zip the files in the QL 2. Copy them to a DOS or QL disk 3. Store them on a QXL.WIN partition 4. Unpack... That way you're absolutely sure that you can run them with QPC.. Alternatively 1. Extract the headers 2. Copy the files to a DOS Disk (with header files) 3. Copy them onto the QXL.WIN drive 4. Reassemble the files/headers Run them Phoebus
Re: [ql-users] Turbo Compiled Programs - crib
??? 30/10/2002 6:35:44 ??, ?/? Fabrizio Diversi [EMAIL PROTECTED] ??: Crib work using my copy of QPC 3.03, I taken it from the list loaded with a=respr(32976) and saved back with : sexec ram1_crib_exe,a,32976,1 And it run quite well Ciao So it was what I believed. lost headers and copied from a DOS disk ;-) Phoebus
Re: [ql-users] Turbo Compiled Programs - crib
I forgot a statement : Crib work using my copy of QPC 3.03, I taken it from the list loaded with - a=respr(32976) - lbytes ram1_crib,a and saved back with : - sexec ram1_crib_exe,a,32976,1 And it run quite well Ciao --- Fabrizio Diversi [EMAIL PROTECTED] wrote: Crib work using my copy of QPC 3.03, I taken it from the list loaded with a=respr(32976) and saved back with : sexec ram1_crib_exe,a,32976,1 And it run quite well Ciao --- Öïßâïò Ñ. Íôüêïò [EMAIL PROTECTED] wrote: Ôçí 31/10/2002 5:37:16 ìì, ï/ç Arnold Clarke [EMAIL PROTECTED] Ýãñáøå: Áðü: Arnold Clarke [EMAIL PROTECTED] Ðñïò: [EMAIL PROTECTED] ÈÝìá: Re: [ql-users] Turbo Compiled Programs Çìåñïìçíßá:Thu, 31 Oct 2002 22:37:16 - Arnold I am afraid that you need to zip them first and send them later... Rich only has a PC which means he will have no means of running the program as you already killed its headers... If you cannot zip it, better use the QL headers program from Dilwyn's website before you send it again (OFF list) Phoebus __ Do you Yahoo!? HotJobs - Search new jobs daily now http://hotjobs.yahoo.com/ __ Do you Yahoo!? HotJobs - Search new jobs daily now http://hotjobs.yahoo.com/
Re: [ql-users] Turbo Compiled Programs - crib
??? 30/10/2002 6:54:59 ??, ?/? Fabrizio Diversi [EMAIL PROTECTED] ??: I forgot a statement : Crib work using my copy of QPC 3.03, I taken it from the list loaded with - a=respr(32976) - lbytes ram1_crib,a and saved back with : - sexec ram1_crib_exe,a,32976,1 And it run quite well Ciao Oh I figured that out... I'm dumb but not THAT dumb ;-) hehehe :-) Phoebus
RE: [ql-users] Turbo Compiled Programs
Hi Rich, if the 'executable' is something like Visual Basic, or any of the .NET stuff, or JAVA, then I believe that it can be done quite simply - because these langauages are interptreted (regardless of what MicxroSoft say on the matter). If the executable is a proper executable which was compiled down from source code to machine code, it is not so easy - certain optimisations may have changed the layout of the code, loops may have been unrolled etc etc - so it is very difficult. The best I've seen was a Windows disassembler which managed to decode all the calls to Windows routines and was thus able to show them as they were in the source, but the rest of the stuff is still in assembly language. Cheers, Norman. - Norman Dunbar Database/Unix administrator Lynx Financial Systems Ltd. mailto:Norman.Dunbar;LFS.co.uk Tel: 0113 289 6265 Fax: 0113 289 3146 URL: http://www.Lynx-FS.com - -Original Message- From: [EMAIL PROTECTED] [mailto:RWAPSoftware;aol.com] Sent: Tuesday, October 29, 2002 12:27 PM To: [EMAIL PROTECTED] Subject: [ql-users] Turbo Compiled Programs I know that one of the problems which any modern QL system faces is the users desire to use existing programs, rather than upgrade to new programs and need to follow a steep learning curve. Whatever happens, this means that to many people, QPC2 or the emulators are too difficult to use, because they will not work easily with x,y and z programs. We therefore need a way of maintaining and upgrading existing programs. We have plenty of assembly language tools (DEAssembler is excellent for getting the source code for a machine code program). However, many of the early commercial programs have been compiled with either Turbo or QLiberator. Is there any way of writing a program which will generate the source code for compiled programs?? -- Rich Mellor RWAP Software 35 Chantry Croft, Kinsley, Pontefract, West Yorkshire, WF9 5JH TEL: 01977 610509 http://hometown.aol.co.uk/rwapsoftware This email is intended only for the use of the addressees named above and may be confidential or legally privileged. If you are not an addressee you must not read it and must not use any information contained in it, nor copy it, nor inform any person other than Lynx Financial Systems or the addressees of its existence or contents. If you have received this email and are not a named addressee, please delete it and notify the Lynx Financial Systems IT Department on 0113 2892990.
