You are not logged in. You can browse in the PowerBASIC Community, but you must click Login (top right) before you can post. If this is your first visit, check out the FAQ or Sign Up.
Both versions of flowchart included in this Word 2003 file.
Stan, I was about to post my own flowchart when.. guess what?
One grey area is the lexer/DDmanager, where do you see the functional divide here? I could not see it so left the DD manager out, but there is something to be explored here I think.
Stan, I was about to post my own flowchart when.. guess what?
One grey area is the lexer/DDmanager, where do you see the functional divide here? I could not see it so left the DD manager out, but there is something to be explored here I think.
Version 3 of the flowchart. You're right, the manager is redundant. With SQL each module can make it's own calls to the DD. I downloaded Don Dickinson's SQLite PB wrappers -- that may be all we need as far as an actual DD manager.
It looks to me like the Lexer is getting bigger, too.
The main module: building a memory image of the target, converting unambiguous code directly, inserting DD objects where the specific language modules have to do a more detailed translation.
Thinking out loud again:
Some kind of memory image template will have to be built from DD information. If we assume (for the first release) that the VB source follows the MS recommended coding and comment conventions there should be enough information to guide the translation -- perhaps a message to the user if it's too ambiguous to automate?
I have not used those, a) are they current b) are they a straight wrapper for the sqlite3 functions, or a little more? I am using Jose Roca's wrappers which he keeps up to date - I'll post that link in a minute. Don't mind whose we use except that they have to be maintained. SQLite currently at 3.5.9.
Some kind of memory image template will have to be built from DD information. If we assume (for the first release) that the VB source follows the MS recommended coding and comment conventions there should be enough information to guide the translation -- perhaps a message to the user if it's too ambiguous to automate?
Stan, you will have to spell that one out for me, I don't understand.
...
I am using Jose Roca's wrappers which he keeps up to date - I'll post that link in a minute. Don't mind whose we use except that they have to be maintained. SQLite currently at 3.5.9.
I didn't know Jose had SQLite stuff. Don's stuff is out of date (PB6.1). I vote for Jose's stuff just based on his name and reputation!
... in the sense of not converting anything at all? That way the back end (PB writer) does ALL the translation.
exactly.
Quote:
Originally Posted by StanHelton Some kind of memory image template will have to be built from DD information. If we assume (for the first release) that the VB source follows the MS recommended coding and comment conventions there should be enough information to guide the translation -- perhaps a message to the user if it's too ambiguous to automate?
Stan, you will have to spell that one out for me, I don't understand.
BTW sorry about the dll!
Not a problem. It's the way my brain works: make it as complex as possible in the first try then take out everything you don't actually need.
If we're thinking of building the target PB code all in RAM, then a template (or maybe just a good set of rules?) might speed things up -- let the Lexer plug in where it finds exact equivalents and leave spaces where the backend modules can put in everything else.
I'm trying to figure out in my head how the Lexer passes information to the backend modules.
Do not go quiet into that good night,
... Rage, rage against the dark.
whew! everything we talk about gets bigger and bigger.
Meanwhile, v3.1 of the flowchart. You will notice some pretty big holes. After reading over Chris' technical issues post, I realized the procedures need to be broken down quite a bit more. It won't hurt my feelings if you decide to wait til v4 of the flowchart comes out before you upgrade.
One more thing, the support cycle for v1 and v2 officially ends tonight at midnight. You will no longer be able to buy retail copies of flowchart-1 or flowchart-2. It is strongly recommended that all registered users upgrade to the newer dotNET, uh..... er.... I mean flowcharts as soon as possible.
Stan
*actually there's no v3.1. I'm wrestling with v4 now.
* oh, and one more thing -- NO apologies to MS for that little joke.
Do not go quiet into that good night,
... Rage, rage against the dark.
Need feedback. Would like one of these to be our working guide.
Hi Stan, viewing your .doc with Open Office, looks like all the V2 symbols have fallen in a heap to the bottom of the page. Please could you post or send a pdf?
I may have missed any discussion of this, but has one been designed? hinted at?
I'm looking at the front end design and we will need the user to tell us the application name, from which source file names will be derived and sent to the lexer, so it could be as simple as putting an application name on the command line, but this has to fan out into a series of filenames. Fred has been posting sets of VB code comprising
are there any others? Do they always share the application name? Fred, you don't appear to process the .wbw (workspace) file, do we need it, or is the information duplicated elsewhere?
Hi Stan, viewing your .doc with Open Office, looks like all the V2 symbols have fallen in a heap to the bottom of the page. Please could you post or send a pdf?
First let me say, "I hate MS Word 2007!"
Here's the PDF. It didn't convert cleanly, but I've cleaned it up so that you can see everything.
Thanks Stan, for my money it's porpoised version 2, because as I pointed out earlier, you can't map VB to PB tokens until you know which flavour of PB you are translating to.
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, and to analyze site activity. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Tweet
Comment