of Motif, and from their
builder tools.
Peter is looking for C and C++ programmers, and I have been told by him that
he is paying good dollar for salaries.
I asked Peter for a better description of the job, and he sent me this:
Integrated Computer Solutions, Inc. (ICS), the leader in advanced
Thank you for all the helpful comments and information. I am now
much better prepared to justify my choice.
It is a little difficult to tally your opinions as votes, but I will
try to group them in dominant categories.
The most common advantage mentioned for C++ was reusable
Chris writes:
You should never use C++ in a real-time situation, simply becasue the
constructors and destructors will be continually allocating memory,
which is completely non-deterministic. A real-time system needs to be
deterministic.
Allocation and deallocation is actually
On Monday, May 30th 2005 at 09:35 -0400, quoth Bill Freeman:
=Chris writes:
= You should never use C++ in a real-time situation, simply becasue the
= constructors and destructors will be continually allocating memory,
= which is completely non-deterministic. A real-time system needs
Bill Freeman wrote:
...
Allocation and deallocation is actually under your control,
and can be no more burden than in C. For example, an local variable
that is an instance gets created on the stack, just like a C structure
that is a local variable. The class itself might have pointers
Steven W. Orr wrote:
I am not a c++ wiz, but I always thought that that was a fundamental
problem. How do you create a class that doesn't always call new if you
know that the lifetime of the storage would be appropriate for the stack
in certain cases?
You can allocate a class on the stack
You should never use C++ in a real-time situation, simply becasue the
constructors and destructors will be continually allocating memory,
which is completely non-deterministic. A real-time system needs to be
deterministic.
Jim Kuzdrall wrote:
Greetings All,
A military client
Bill McGonigle wrote:
On May 27, 2005, at 11:48, Jim Kuzdrall wrote:
The stipulations were: 1) use Linux; 2) use C++.
Sounds like they want well-debugged code. 99.99 % of the time the STL
classes are better than ones you'd write on a 1-off basis, both in
terms of being debugged
). The guys with stars on their
shoulders don't actually know what OS it is - they're concerned with
the application-level buzzwords, not the geek stuff. Oh, and their
systems are C++ based. Note for the audience - if you're doing
military work get yourself a decent version control system and a good
On Fri, May 27, 2005 at 05:19:18PM -0400, Jerry Feldman wrote:
In the case of C++, you have a class that overloads + as a concatenation
operator. Additionally, the resultant variable c is expandable. In C, one
must make sure that a sufficient sized array is allocated for the result.
Said
:5: syntax error before '/' token
laura$
(And I'm still joking. :):)
For the record, C99 standardized // comments in C. Compiling with
-std=c99 produces no error, though -std=c89 does produce an error.
-- Bob
___
gnhlug-discuss mailing list
On Sat, 28 May 2005 12:17:26 -0400
Bob Bell [EMAIL PROTECTED] wrote:
For the record, C99 standardized // comments in C. Compiling with
-std=c99 produces no error, though -std=c89 does produce an error.
Many C compilers allow the // comments unless you are compiling in
strict C89 mode
On Sat, 28 May 2005 12:12:06 -0400
Bob Bell [EMAIL PROTECTED] wrote:
What you choose may depend on which of those descriptions matches what
you want for a particularly project. For instance, there's a reason
most OS kernels are written in C.
C was designed specifically as an implementation
Greetings All,
A military client arbitrarily added 2 contract requirements which I
have the opportunity to change. I need some advice from your
collective experience to make certain I don't regret my choice a year
from now.
The stipulations were: 1) use Linux; 2) use C
now.
=
=The stipulations were: 1) use Linux; 2) use C++.
=
=The system is an embedded 32-bit DSP-type microcontroller (of my
=choice) with about 1 megabyte of code. It is battery operated and uses
=prioritized, real-time interrupts to meet response time criteria. The
=software functions
On Friday 27 May 2005 11:48 am, Jim Kuzdrall wrote:
C++ versus C is my quandary. Can anyone give me good reasons for
choosing one over the other in this case. Opinions are welcome, but I
must have a list of reasons ready if my choice is questioned.
Very quickly, C++ might be a better
If it were me I'd pick a candidate DSP and then go
and find mailing lists and USENET newsgroups oriented
around that processor where folks are discussing projects
similar to mine. I might end up learning that C or C++
support is better or worse than expected, or which of
the available execs
On May 27, 2005, at 11:48, Jim Kuzdrall wrote:
The stipulations were: 1) use Linux; 2) use C++.
Sounds like they want well-debugged code. 99.99 % of the time the STL
classes are better than ones you'd write on a 1-off basis, both in
terms of being debugged and in terms of performance
On Fri, 27 May 2005 11:48:52 -0400
Jim Kuzdrall [EMAIL PROTECTED] wrote:
The stipulations were: 1) use Linux; 2) use C++.
If it were me I'd go with C++. C++ allows better commenting.
Besides, and seriously, the better business decision as embodied
in going with the client's stipulations
On 5/27/05, Bill Sconce wrote:
If it were me I'd go with C++. C++ allows better commenting.
How so?
[EMAIL PROTECTED] mda]$ gcc -Wall -o hello foo.c
[EMAIL PROTECTED] mda]$ cat foo.c
#include stdio.h
int main(int argc, char *argv[])
{
printf(hello world\n);
// std beginner program
return
On Fri, 27 May 2005 14:55:58 -0400
Jeff Macdonald [EMAIL PROTECTED] wrote:
On 5/27/05, Bill Sconce wrote:
If it were me I'd go with C++. C++ allows better commenting.
How so?
Because of the // form. You guessed the purpose of my joke correctly.
But your command string was buggy
Jerry Feldman [EMAIL PROTECTED] writes:
As far as performance, C generally gives you better performance. but C
programmers tend to be skimpy with comments and tend to write tricky code.
That seems to be a feature of any given programmer. Since Jim is
going to be the programmer regardless
On Friday 27 May 2005 4:46 pm, Paul Lussier wrote:
Jerry Feldman [EMAIL PROTECTED] writes:
As far as performance, C generally gives you better performance. but C
programmers tend to be skimpy with comments and tend to write tricky
code.
That seems to be a feature of any given programmer
On Fri, 27 May 2005 16:46:20 -0400
Paul Lussier [EMAIL PROTECTED] wrote:
FWIW, I'd go with C, just because there's at least some
standardization for C and therefore, among compilers, whereas there
isn't with C++, which would allow for somewhat better potability if
that's important
On 5/27/05, Bill Sconce wrote:
If it were me I'd go with C++. C++ allows better commenting.
One concern is setting (and clearing) the microprocessor's interrupt
mask in C++. The code contains processes should not be interrupted
during a critical step. Some compilers are strict
25 matches
Mail list logo
