This is the mail archive of the ecos-patches@sourceware.org mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: POSIX threads early startup C++ exceptions


> I'm decompressing an FPGA image while programming an FPGA. There are
> *many* things that can go wrong and this code is *greatly* simplified
> by having exceptions.

This probably is just going to come down to a difference of opinion, but in
my view exceptions are meant to be exactly that - things that are out of
the ordinary and should not happen in the normal course of events. HAL
initialisation should either work or fail. Exceptions should not be used as
intra-program communication.,

I believe this decision should be made by the programmer who develops the application and eCos should give him that choice.

(ROM space), but does not need to add much data (RAM space). Your change
adds over half a K of data to every POSIX library user. All to support one
implementation of one particularly early running driver, solely at
initialisation time, and not thereafter.

512 bytes? I didn't realize. That is a bit on the high end, yes. Not entirely intentional on my part so I would have to examine where that happened(now moot since the change won't be accepted anyway, i.e. it is too application specific).

eCos is open source so you have the freedom of making changes like this. It
doesn't mean that every change needs to be contributed back for all to use,
particularly if it is highly specialised.

Anyway, I've said my bit. I suspect unfortunately we may have to agree to
disagree.

Yup, no problem there.


--
Øyvind Harboe
http://www.zylin.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]