It looks like Python's days are numbered; I just read on Slashdot
about a programming language that uses *only* whitespace:
http://compsoc.dur.ac.uk/whitespace/
I expect that most current Python programmers will have switched over
by the end of the year.
Any die-hard fanatics left over will
David Megginson wrote:
It looks like Python's days are numbered; I just read on Slashdot
about a programming language that uses *only* whitespace:
http://compsoc.dur.ac.uk/whitespace/
Knowing the python developer base a little, I think they might have
implemented this in a couple of hours
I am waiting for the programming language for amateur radio operators,
Morse. There is nothing like programming in dots and dashes!
On Tuesday, April 1, 2003, at 06:11 AM, David Megginson wrote:
It looks like Python's days are numbered; I just read on Slashdot
about a programming language
On Tue, 01 Apr 2003 14:39:22 +0200,
Erik Hofman [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]:
David Megginson wrote:
It looks like Python's days are numbered; I just read on Slashdot
about a programming language that uses *only* whitespace:
I am waiting for the programming language for amateur radio operators,
Morse. There is nothing like programming in dots and dashes!
. -.-- --..-- - .- - .. ... -. .. -.-. . .-.-.-
g. (kc7afe)
On Tuesday, April 1, 2003, at 06:11 AM, David Megginson wrote:
It looks like
Now that we're rearranging the /controls/ subtree, it might be a good
time to clean up the naming.
1. Consistency
--
Most of the property names use lower case and hyphens ('-') as word
separators. I suggest that we fix the following to be consistent:
/controls/flight/BLC
David Megginson wrote:
Now that we're rearranging the /controls/ subtree, it might be a good
time to clean up the naming.
I am all for (property naming) consistency and I am for selecting the
tree layout now, and stick with it from now on.
There are a few property names I wouldn't have chosen,
On Tue, 1 Apr 2003 07:12:36 -0600,
Jonathan Polley [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]:
On Tuesday, April 1, 2003, at 06:11 AM, David Megginson wrote:
It looks like Python's days are numbered; I just read on Slashdot
about a programming language that uses *only*
Jonathan Polley writes:
I am waiting for the programming language for amateur radio operators,
Morse. There is nothing like programming in dots and dashes!
.. -.. --- -. - --. . - .. -
All the best,
David
--
David Megginson, [EMAIL PROTECTED], http://www.megginson.com/
I am very happy that we are reorganizing the mess under /controls, but
unfortunately, we've landed in a bit of a deeper mess that will need
some fixing. The changes just committed for the base package are
extremely incomplete: many of the YASim flight models under
Aircraft-yasim/ and many of the
You could conceivably write any language in Morse, you just need to run a .- to
ASCII converter over the source before the compiler.
I suppose it would be called -.2a
Richard
-Original Message-
From: Jonathan Polley [mailto:[EMAIL PROTECTED]
Sent: 01 April 2003 2:13 pm
To: [EMAIL
For me, FlightGear just dies with the message FlightGear aborted for
JSBSim models or simply Aborted for yasim models. :-(
I'm totally dead in the water here. This needs to get resolved quickly.
Curt.
David Megginson writes:
I am very happy that we are reorganizing the mess under /controls,
David Megginson writes:
Now that we're rearranging the /controls/ subtree, it might be a good
time to clean up the naming.
1. Consistency
--
Most of the property names use lower case and hyphens ('-') as word
separators. I suggest that we fix the following to be consistent:
David Megginson writes:
It looks like Python's days are numbered; I just read on Slashdot
about a programming language that uses *only* whitespace:
http://compsoc.dur.ac.uk/whitespace/
I expect that most current Python programmers will have switched over
by the end of the year.
Any
David Megginson wrote:
Unfortunatelly my ISP decided it would be funny to shut down my internet
connection just after I uploaded the new files today.
I presume you started to hunt them down already?
I've been digging through a number of files as well, and think we should
continue now. BAcking
I am waiting for the programming language for amateur radio operators,
Morse. There is nothing like programming in dots and dashes!
.. -.. --- -. - --. . - .. -
uet? Eh? ITYM, --. ... . HTH, HAND!
g.
___
Flightgear-devel mailing list
Boy, talk about the ultimate in obfuscated C programming...
On Tue, 1 Apr 2003, Richard Bytheway wrote:
You could conceivably write any language in Morse, you just need to run a .- to
ASCII converter over the source before the compiler.
I suppose it would be called -.2a
Richard
Curtis L. Olson wrote:
For me, FlightGear just dies with the message FlightGear aborted for
JSBSim models or simply Aborted for yasim models. :-(
I'm totally dead in the water here. This needs to get resolved quickly.
The lates CVS version of the base package and FlightGear *and* a
complete
On Tue, 01 Apr 2003 19:00:30 +0200
Erik Hofman [EMAIL PROTECTED] wrote:
Curtis L. Olson wrote:
For me, FlightGear just dies with the message FlightGear
aborted for
JSBSim models or simply Aborted for yasim models. :-(
I'm totally dead in the water here. This needs to get
resolved quickly.
The
David Megginson [EMAIL PROTECTED] said:
I am very happy that we are reorganizing the mess under /controls, but
unfortunately, we've landed in a bit of a deeper mess that will need
some fixing. The changes just committed for the base package are
extremely incomplete: many of the YASim flight
Jon S Berndt wrote:
On Tue, 01 Apr 2003 19:00:30 +0200
Erik Hofman [EMAIL PROTECTED] wrote:
Curtis L. Olson wrote:
For me, FlightGear just dies with the message FlightGear aborted for
JSBSim models or simply Aborted for yasim models. :-(
I'm totally dead in the water here. This needs to get
Jim Wilson wrote:
David Megginson [EMAIL PROTECTED] said:
I am very happy that we are reorganizing the mess under /controls, but
unfortunately, we've landed in a bit of a deeper mess that will need
some fixing. The changes just committed for the base package are
extremely incomplete: many of
Erik Hofman writes:
Jon S Berndt wrote:
On Tue, 01 Apr 2003 19:00:30 +0200
Erik Hofman [EMAIL PROTECTED] wrote:
Curtis L. Olson wrote:
For me, FlightGear just dies with the message FlightGear aborted for
JSBSim models or simply Aborted for yasim models. :-(
I'm totally dead in
How do I reenable debugging output?
Thanks,
Curt.
--
Curtis Olson IVLab / HumanFIRST Program FlightGear Project
Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED]
Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org
Erik Hofman writes:
There are a few property names I wouldn't have chosen, but I think it
would be of the greatest importance to pick one, and get over it ;-)
Thanks for reminding me -- the propeller-pitch property is misnamed,
and we should try to think of something more descriptive (it
Curtis L. Olson writes:
For me, FlightGear just dies with the message FlightGear aborted for
JSBSim models or simply Aborted for yasim models. :-(
I'm totally dead in the water here. This needs to get resolved quickly.
Through the magic of Emacs and etags, I was able to replace
David Megginson writes:
Curtis L. Olson writes:
For me, FlightGear just dies with the message FlightGear aborted for
JSBSim models or simply Aborted for yasim models. :-(
I'm totally dead in the water here. This needs to get resolved quickly.
Through the magic of Emacs and
Curtis L. Olson writes:
How do I reenable debugging output?
maybe
main.cxx
static bool fgMainInit( int argc, char **argv ) {
// set default log levels
sglog().setLogLevels( SG_ALL, SG_INFO );
___
Flightgear-devel mailing list
[EMAIL
David Megginson writes:
Thanks for reminding me -- the propeller-pitch property is misnamed,
and we should try to think of something more descriptive (it directly
controls propeller speed, not pitch).
Not that we don't want a new name but aren't these two
(pitch, propellor speed) the
On Tue, 2003-04-01 at 13:28, Norman Vine wrote:
David Megginson writes:
Thanks for reminding me -- the propeller-pitch property is misnamed,
and we should try to think of something more descriptive (it directly
controls propeller speed, not pitch).
Not that we don't want a new name
Norman Vine wrote:
Curtis L. Olson writes:
How do I reenable debugging output?
maybe
main.cxx
static bool fgMainInit( int argc, char **argv ) {
// set default log levels
sglog().setLogLevels( SG_ALL, SG_INFO );
That was one of the things in the back of my head which needed to be
Erik Hofman [EMAIL PROTECTED] said:
Jim Wilson wrote:
David Megginson [EMAIL PROTECTED] said:
I am very happy that we are reorganizing the mess under /controls, but
unfortunately, we've landed in a bit of a deeper mess that will need
some fixing. The changes just committed for the base
Greetings!
I'm trying to install SimGear-0.3.0, but camera.hpp is missing. Would
someone please post that file. I've searched the internet to no avail.
Thanks!
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
Norman Vine writes:
Curtis L. Olson writes:
How do I reenable debugging output?
maybe
main.cxx
static bool fgMainInit( int argc, char **argv ) {
// set default log levels
sglog().setLogLevels( SG_ALL, SG_INFO );
Yes, but this was reworked so it could be done from the
I tracked down my crash to controls-bind()
There you will find a plethora of places where the code is sprintf'ing
to a char[32] array, but the contents is often longer than 32 bytes.
Might not have been crashing everyone else (building with -g?) but it
was crashing with -O2. Fixed in cvs ...
Curtis L. Olson wrote:
I'm still dead in the water. I appear to be dying somewhere in
fgInitSubsystems()
How the heck can I reenable debugging output?!?
I see there is a --log-level option in options.cxx but it's not
described in --help --verbose and using it seems to have no effect.
Do you use
Norman Vine writes:
Not that we don't want a new name but aren't these two (pitch,
propellor speed) the ~same~ thing assuming a variable pitch prop
No. With a variable-pitch prop, the rpm will vary with both the pitch
setting and the throttle setting, but those have not been in use for
70
Erik Hofman [EMAIL PROTECTED] said:
And I don't think it's fair to demand a
painles recompile of the *developers* version of FlightGear every minute
of the day.
Agree with all you said, except maybe this. Demand is one thing, expect
is another. It is fair to demand it. I'm not talking
Erik Hofman writes:
Whta is happening is there is a pint where the --log-level option
actually starts working (inside fgMainLoop() ) but before that the log
level is set by the line Norman pointed out.
We also seem to have a variety of ways to set logging. In main.cxx,
there is code
Curtis L. Olson wrote:
I tracked down my crash to controls-bind()
There you will find a plethora of places where the code is sprintf'ing
to a char[32] array, but the contents is often longer than 32 bytes.
Might not have been crashing everyone else (building with -g?) but it
was crashing with
David Megginson wrote:
We also seem to have a variety of ways to set logging. In main.cxx,
there is code that uses the property
/sim/log-level
with an integer value.
However, in fg_props.cxx, FlightGear also uses
/sim/logging/priority
/sim/logging/classes
with string values (I added
Curtis L. Olson writes:
You bastards! Writing property names to char arrays that are too short for
the data you are putting in it. :-( Fixed ...
for (index = 0; index MAX_ENGINES; index++) {
! char name[32];
sprintf(name, /controls/engines/engine[%d]/throttle, index);
David Megginson writes:
With a constant-speed prop, the governor will attempt
to maintain a constant RPM across a range of throttle settings by
constantly varying the propeller pitch.
I think you just uncovered your new name
Note that 'constant-speed' is not mentioned in the original post
If you have a machine to run this on :-)
http://www.daionet.gr.jp/~masa/rthdribl/index.html
Norman
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItemitem=2167383299
--
Curtis Olson IVLab / HumanFIRST Program FlightGear Project
Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED]
Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org
Jim Wilson wrote:
Erik Hofman [EMAIL PROTECTED] said:
And I don't think it's fair to demand a
painles recompile of the *developers* version of FlightGear every minute
of the day.
Agree with all you said, except maybe this. Demand is one thing, expect
is another. It is fair to demand it.
Erik Hofman writes:
However, in fg_props.cxx, FlightGear also uses
/sim/logging/priority
/sim/logging/classes
with string values (I added those a long time ago). I'm not sure how
the two interact.
I thought these were for property logging?
No, that's controlled
Erik Hofman writes:
Is there still no replacement function to do this kind of operation in a
C++ string?
strstream would do the trick, but not all compilers support it yet.
All the best,
David
--
David Megginson, [EMAIL PROTECTED], http://www.megginson.com/
On Tue, 1 Apr 2003 13:16:19 -0600,
Curtis L. Olson [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]:
http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItemitem=2167383299
..looks like a fellow modeller:
On Tue, 2003-04-01 at 08:21, Erik Hofman wrote:
David Megginson wrote:
Now that we're rearranging the /controls/ subtree, it might be a good
time to clean up the naming.
I am all for (property naming) consistency and I am for selecting the
tree layout now, and stick with it from now on.
On Tue, 2003-04-01 at 07:29, Curtis L. Olson wrote:
David Megginson writes:
It looks like Python's days are numbered; I just read on Slashdot
about a programming language that uses *only* whitespace:
http://compsoc.dur.ac.uk/whitespace/
I expect that most current Python
On Mon 31. March 2003 19:53, you wrote:
Martin Dressler wrote:
I made some investigations in last days and find why my textures look
so bad when scaled down to 128x128 textures compared to textures
generated by perl scripts (writen by Andy?)
Uh, once upon a time, yeah. They're terrible
The magnetos are now defaulted to position 2 (Left) instead of 0 (Off). Was
that intentional? Is there anything else in global preferences not mentioned
in the log?
Best,
Jim
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
Jim Wilson writes:
Erik Hofman [EMAIL PROTECTED] said:
And I don't think it's fair to demand a
painles recompile of the *developers* version of FlightGear every minute
of the day.
Agree with all you said, except maybe this. Demand is one thing, expect
is another. It is fair to
David Megginson wrote:
Erik Hofman writes:
However, in fg_props.cxx, FlightGear also uses
/sim/logging/priority
/sim/logging/classes
with string values (I added those a long time ago). I'm not sure how
the two interact.
I thought these were for property logging?
* [EMAIL PROTECTED] (David Megginson) [2003.04.01 13:31]:
You can set /sim/logging/classes to a whitespace-separated list of any
or all of the following values:
terrain
astro
flight
input
gl
view
cockpit
general
math
event
aircraft
autopilot
io
clipper
56 matches
Mail list logo
