Well, from what I see here is a business opportunity. If everyone that is interested in achieving this (and willing to pay). Then I would suggest a group should be formed andcreate a well defined set a specifications.
I am sure that Chipp at Altuit or someone else would be able to produce the much desired solution but for a price. This would be the quickest way of getting exactly what is being asked for in the shortest period of time. I would be glad to coordinate (off the list ) creating the product specifications and then putting it out to bid. ...any takers? Please contact me off the list. regards, Glen On 6/22/05, MisterX <[EMAIL PROTECTED]> wrote: > Derek, > > Not to mean that i have all the answers (but i've tried to answer all the > questions in this respect before). I know C pretty well but i hate it any > time you have to debug anything like pointer increments or loookup tables. > Note that C compilers (not hte free ones) usually have great debugging tools > (no comparison to rev). > > The translation to C is EASY! To C++, like Java or Javascript is a nightmare > however... Add pointers and you got HELL! It's kind of the same problem with > dot notation of object-oriented variables object.property->value or all it's > variations > > If you managed it, it could work but would it be optimized? Most compilers > use repeated passes to compile to assembler and then again to machine > language (if that's still current for some compilers) but for a program to > create a more efficient code than a coder, you can forget it. > > a program in C is NOT like a program in Rev and vice versa - except for a > few "data crunching" routimes. > > I thought (still haven't stopped) of doing this in Python. It's doable. But > i have a vendeta with VBS and Active directory at work to get rid of first. > Then i can translate it easier to Python. With the right wrappers we should > then have any compiler (python, c, fortran, etc.). > > But first write the translator translator - eh, language codec ;) > What's next, language drivers ? tttt. got those already! These are xtalk-c > or c-xtalk compatibility handlers - makes scripts darn easier to translate > in the first place - In the xtalk to C example, you just need to #include > axtalk.c library in your code. But this is still "vapor" as i hate the c > debugging. > > cheers > Xavier > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of > > Derek Bump > > Sent: Wednesday, June 22, 2005 16:19 > > To: How to use Revolution > > Subject: Re: compileIt for revolution? > > > > I have spoke with a few individuals in regards to creating a > > utility for Revolution that would convert Transcript to C. > > Unfortunately, I know little of C and the individuals I > > talked with were not ready to start a project such as what you want. > > > > But...it is possible. > > > > If one who knows C and could figure out some sort of > > Transcript wrapper, then it would be possible. There are > > many freeware and public domain compilers out there, but > > finding one that successfully compiles DLLs for Revolution is > > seemingly difficult. I've been trying for a few months now, > > but with my limited knowledge of C I end up running into errors. > > > > I am working on this project, but the *confusing* Externals > > SDK doesn't help. It's pretty bad when I've used about 10 > > different compilers (including MS Visual C) and I still can't > > get the samples to compile properly. But that's a whole > > different issue. > > > > > > Derek Bump > > Dreamscape Software > > _______________________________________________ > > Compress Photos for the Web with JPEGCompress > > http://www.dreamscapesoftware.com/ > > _______________________________________________ > > use-revolution mailing list > > [email protected] > > Please visit this url to subscribe, unsubscribe and manage > > your subscription preferences: > > http://lists.runrev.com/mailman/listinfo/use-revolution > > > > _______________________________________________ > use-revolution mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-revolution > _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
