> From: [email protected] [mailto:[email protected]] > On Behalf Of Philippe Gerum > Sent: Sunday, September 18, 2011 5:37 PM > ... > Actually, we used to follow strictly the pSOS convention for this until > 2.4.x, at which point we moved to name strings precisely because > non-null terminated char[4] arrays would break the registry, the way you > described. This is one of the rare situations where mimicking a useless > limitation of the original API may be challenged by usability concerns > in the new environment, and usability won in that case. The problem > mostly comes from the fact that char[4] is automatically convertible to > const char *, so we have no warning/error leading us to check the > potentially problematic call sites. > > The concern about moving back to char[4] arrays - null-terminated if > shorter - is for people who currently assign strings longer than 4 > characters to name their objects. What could be done, is providing a > build switch to select the accepted input, like > --disable-psos-long-names to turn on char[4] interpretation.
While I would prefer the switch --enable-psos-long-names, this sounds okay to me, the more so as it is more than people who use the pSOS skin without obeying pSOS rules deserve. -- Regards, Dietmar ________________________________________ manroland AG Vorsitzender des Aufsichtsrates: Hanno C. Fiedler Vorstand: Gerd Finkbeiner (Vorsitzender), Dr. Ingo Koch, Dr. Markus Rall, Paul Steidle Sitz der Gesellschaft: Offenbach am Main, Registergericht: Amtsgericht Offenbach HRB-Nr. 42592 USt-Ident-Nr. DE 250200933 _______________________________________________ Xenomai-help mailing list [email protected] https://mail.gna.org/listinfo/xenomai-help
