- static vector (c style) - 1 Update
- XML Schema to C++ - 1 Update
| Christopher Pisz <nospam@notanaddress.com>: Jan 26 04:30PM -0600 On 1/12/2015 8:30 AM, alessio211734 wrote: > ... > static NearData nearCells[32]; > }; After all the discussion of profiling and virtual functions in child threads, ....I still want to know why in the world anyone would want a static C-Array in their C++ class. I'd sure like to know how the author intended to use this class, because I question both making it static and using the c-array vs a stl container. |
| Christopher Pisz <nospam@notanaddress.com>: Jan 26 04:27PM -0600 On 1/25/2015 10:29 AM, mike myers wrote: > XML processing has turned into a common task that lots of C application designers suffer from. Using low-level XML access APIs for example DOM and SAX is tiresome and error-prone, specifically for large XML vocabularies. XML Data Binding is really a new alternative which automates a lot of the job by showing the data saved in XML like a statically-typed, vocabulary-specific object model. > http://www.liquid-technologies.com/xmldatabinding/xml-schema-to-cpp.aspx Ok, maybe Who made the CPerson class? It's generated? If so, what's it look like? Do I derive from it to add my functionality? How do we know your library is free of memory leaks? "using reference counting classes" could mean someone rolled their own reference counting mechanism, which makes me trust it less rather than more. How many people are using it and how much testing was done on it. It would really stink to dig into a new not so popular library and find out after building on it quite a bit that it leaks. That's been my experience with _alot_ of XML libs in the past. |
| You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page. To unsubscribe from this group and stop receiving emails from it send an email to comp.lang.c+++unsubscribe@googlegroups.com. |
No comments:
Post a Comment