This is the mail archive of the
ecos-patches@sourceware.org
mailing list for the eCos project.
AW: [PATCH] Speed-up sprintf() family of functions.
- From: "Neundorf, Alexander" <Alexander dot Neundorf at jenoptik dot com>
- To: <ecos-patches at ecos dot sourceware dot org>
- Date: Wed, 3 Jan 2007 08:54:25 +0100
- Subject: AW: [PATCH] Speed-up sprintf() family of functions.
> Von: ecos-patches-owner@ecos.sourceware.org
> [mailto:ecos-patches-owner@ecos.sourceware.org]Im Auftrag von Sergei
> Organov
>
>
> Jonathan Larmour <jifl@eCosCentric.com> writes:
> > Sergei Organov wrote:
> >> Jonathan Larmour <jifl@eCosCentric.com> writes:
>
> [...]
>
> >>>Therefore I think we have a choice of solutions: we can
> either change
> >>>the pure virtual functions to be something lik e.g.:
> >>>
> >>>virtual Cyg_ErrNo write( const cyg_uint8 *buffer, cyg_ucount32
> >>>buffer_length, cyg_ucount32 *bytes_written ) {
> >>> CYG_FAIL("write method called directly on Cyg_OutputStream");
> >>>}
> >>>
> >>>However even that depends on assertion support being on, so is not
> >>>ideal.
> >>
> >> Why not ideal? Either you want assertions and then you compile with
> >> assertions on, or you don't. I think it's the best way to
> handle this
> >> provided you don't want to bring C++ runtime to every
> application. [I
> >> have my applications in C++, so I do battle with these
> issues anyway]
> >
> > Firstly, since this would be a fundamental problem, if it
> > occurs with assertions off, it could be unnoticed.
>
> The question is how is it different from any other occurrence
> of CYG_FAIL in the eCos source base?
That's what I thought too...
Alex