Real constants

[Russ Srole]

Bob,

Getting further off topic: The big differenct was that the Yugo
was a POS and the Dusenburg was, well a Duzi, hence the saying;
"It's a duzi! (spelling?). If you're ever in the Los Angeles area
go to the Peterson Automotive Museum and see a room full of them.
They are amazing!



------------------

[Bob Zale]

Sure, Danny! The Yugo, was a small, very inexpensive auto imported to the U.S. from Yugoslavia some years back. It quickly gained a reputation as being something less than a technical marvel. I believe it has since gone the way of the Studebaker, Deusenberg...

Regards,

Bob


------------------

Off topic and irrelevant, i know, however can someone tell me
what a Yugo is?

Ta!

Danny (...from England! )

------------------


[This message has been edited by danny greenwood (edited June 04, 2001).]

[Michael Mattias]

Well, I'm certain Mr Edmonds meant to say, "R &D will make that decision after reviewing and considering all the customer requests.

But since he didn't say that, I thought it reasonable to mention that customers do (should) have a huge impact on any product's features.

Even the Yugo.

MCM

[Bob Zale]

[QUOTE]Originally posted by Michael Mattias:
Hmm, I'd have thought it might be the customers' decision.

Customers certainly exercise a purchase decision. And customer opinions are, of course, highly valued and reviewed. But haven't you taken this to a rather unusual level? You truly believe that customers should each design their own PowerBASIC compiler and we should deliver? Would each customer get his own personal version, or would you place yourself in charge to collaborate the design for everyone else?

Tell me, when you bought your last Yugo, did you do the engineering work for them before you took delivery?

Regards,

Bob Zale
PowerBASIC Inc.

------------------

[Michael Mattias]

.. [a new features] is the decision of R&D, not Tech Support, so we'll just have to see what "develops"!

Hmm, I'd have thought it might be the customers' decision.

MCM

[Lance Edmonds]

They have been asked for before, and they are also on the list.

Personally, I believe the use of equates/constants without a leading % or $ symbol adds to the ability to create obfuscated code, so I would not endorse such a feature. However, it is the decision of R&D, not Tech Support, so we'll just have to see what "develops"!

------------------
Lance
PowerBASIC Support
mailto:[email protected][email protected]</A>

[Michael Mattias]

On the same list, do we have constant/equates allowed

1. Without the leading percent sign?
2. In the format:

#define  my_const    500  [(+|OR)|(other_const|literal)]

These features would be very handy for those of us who work with SDK-style programming with dialogs and controls defined in resource files, as it would allow us to #INCLUDE (#include) the same file in both our resource script and program source code.


MCM


[This message has been edited by Michael Mattias (edited June 03, 2001).]

[Lance Edmonds]

Hi David,

PowerBASIC does not support floating-point equates at this time, but this feature request is already on the "wish list"...



------------------
Lance
PowerBASIC Support
mailto:[email protected][email protected]</A>

How do you create a real constant in PB? Integer and
string seem covered nicely, but can't find a solution of reals.