I'm working on the command parser for my Air Traffic Control sim. I have not
written a parser in this sense before.
The parser takes input from the user, and parses it into meaningful
instructions to pass to an aircraft. It emulates a unified ear for the
pilots of all the aircraft.
It deals with
Hi all,
I had a game idea back in the 80s. I feel like it might be a good followup
project after the flight sim, but the idea is fun so I thought I would share
it here and see what others might make of it.
The game occurs in a two-dimensional gravity well. The yellow sun occupies
a fixed point
--
From: QL-MyLink (f/fh) q...@mylink.adsl24.co.uk
Sent: Saturday, February 05, 2011 9:47 PM
To: ql-us...@q-v-d.com
Subject: Re: [Ql-Users] 12th February 2011
What do I know about Derby?
It's where they
What do I know about Derby?
It's where they say Twosdee.
Just outside Derby its Twosdee, ducks,
Just down the road in Nottingham they say Shintin Duck.
John Taylor
___
QL-Users Mailing List
Dave,
ABC C NN - 2 digits is an altitude in thousands of feet
ABC C NN X - the X modifier expedites the altitude change (where
possible/reasonable)
ABC C NNN - 3 digits is a heading in degrees
ABC C NNN L (or R) - where a course change follows the shortest turn, L
or R modifier
For clarity: ABC is the format of the flight number. eg: AAL2123,
CAL2260, FDX1001, etc... Sometimes, there are three digit flights like
BAA418, etc...
I like the way you have the parser call a function to isolate each
component. I have until this point been thinking in terms of...
Also...
One of the major problems I'm having is the manual I downloaded. The
QPCKeywords V1_02 document has many keywords missing/ignored that I
remember, like RIGHT$, LEFT$ and INSTR... and I don't remember how to use
them. I would dig in the garage to find the old printed manual, but it's
Am 06.02.2011 12:19, schrieb Plastic:
Also...
One of the major problems I'm having is the manual I downloaded. The
QPCKeywords V1_02 document has many keywords missing/ignored that I
remember, like RIGHT$, LEFT$ and INSTR... and I don't remember how to use
them. I would dig in the garage to
Tobias, thank you! I have struggled with this for a couple of days. This'll
teach me for having started out on a Commodore PET.
I couldn't find INSTR in this manual because it's in the wrong place. After
IO_PRIORITY. It never crossed my mind to look past the place it would
logically be.
This is
Am 06.02.2011 12:10, schrieb Plastic:
For clarity: ABC is the format of the flight number. eg: AAL2123,
CAL2260, FDX1001, etc... Sometimes, there are three digit flights like
BAA418, etc...
I like the way you have the parser call a function to isolate each
component. I have until this point
On Sun, Feb 6, 2011 at 5:47 AM, Tobias Fröschle
tobias.froesc...@t-online.de wrote:
Am 06.02.2011 12:10, schrieb Plastic:
For clarity: ABC is the format of the flight number. eg: AAL2123,
CAL2260, FDX1001, etc... Sometimes, there are three digit flights like
BAA418, etc...
I like the
For anyone who is following this project:
Build 009 of the driver was completed and tested today. This fully
implements the io.formt trap, meaning that you can now issue the command:
FORMAT USB1_
Note: The Ser-USB format routine is much simpler than the QUBIDE original;
it only
Tobias Fröschle wrote, on 6/Feb/11 11:36 | Feb6:
Am 06.02.2011 12:19, schrieb Plastic:
Also...
One of the major problems I'm having is the manual I downloaded. The
QPCKeywords V1_02 document has many keywords missing/ignored that I
remember, like RIGHT$, LEFT$ and INSTR... and I don't remember
Adrian Ives wrote:
For anyone who is following this project:
Build 009 of the driver was completed and tested today. This fully
implements the io.formt trap, meaning that you can now issue the command:
FORMAT USB1_
Well done Adrian! And thank's for supporting this project. I wish, someone
Tobias helpfully said -
Dave,
the manual is right here and your memory is wrong ;-).
-
Brave Dave,
Do you have a copy of Jan Jones?
It's great for *all* SBasic INSTR-uctions.
John in Wales
Dave,
had a lazy Sunday afternoon and was thinking about your problem - And,
being a bit challenged and had nothing else to do, wrote a
parser/analyzer for your Language:
Ended up with quite a bit of code, the problem is not as simple as it
seems (Hope I didn't over-complicate things). But I
On Sun, Feb 6, 2011 at 11:58 AM, QL-MyLink (f/fh)
q...@mylink.adsl24.co.ukwrote:
Tobias helpfully said -
Dave,
the manual is right here and your memory is wrong ;-).
-
Brave Dave,
Do you have a copy of Jan Jones?
It's
In message 001c01cbc23b$b4caf510$1e60df30$@acanthis.co.uk, Adrian Ives
adr...@acanthis.co.uk writes
Hi Adrian,
Yes, using the USBWiz is a good idea.
A new hardware project always creates interest.
PS - This list is getting very busy, too.
Just catching up on over 100 emails ... :-)
I have
In message 4d45ec4b.7030...@sbcglobal.net, Timothy Swenson
swenso...@sbcglobal.net writes
On 1/30/2011 10:48 AM, Malcolm Cadman wrote:
Were Officers to be elected, directly, at an AGM, it would open the door
to someone incompetent to get voted in, or some collusion to take place.
Wow. You really thought about it. 221 lines of code!
I have this notion that I need to scan through the characters and split the
input into words. I can simplify a lot because the bounds are known and very
limited.
For example, S INSTR cmd$ is a very simple case and so is L - so for
these
221 lines of code!
Tobias, do have more 'lazy Sunday afternoons', please.
Wish I could have written the same - it's poked some valuable ideas into my
memory. Thank you.
In there however, is a small shadow, specifically regarding your SELect
ON's. Does your code rely on the additional
Am 07.02.2011 02:11, schrieb QL-MyLink (f/fh):
221 lines of code!
Tobias, do have more 'lazy Sunday afternoons', please.
Wish I could have written the same - it's poked some valuable ideas
into my memory. Thank you.
In there however, is a small shadow, specifically regarding your
SELect
Am Sonntag, den 06.02.2011, 17:56 -0600 schrieb Plastic:
Let me play with some code and see what I come up with over the next couple
of days. I think I can be a lot more computationally economical, but my code
will not flex easily to other cases, whereas your code is applicable in a
lot of
23 matches
Mail list logo
