One of the absolute worst features of C++ is how it makes a lot of things so context-dependent — which just means that when you look at the code, a local view simply seldom gives enough context to know what is going on.
That is a huge problem for communication. It immediately makes it much harder to describe things, because you have to give a much bigger context. It’s one big reason why I detest things like overloading — not only can you not grep for things, but it makes it much harder to see what a snippet of code really does.
Put another way: when you communicate in fragments (think “patches”), it’s always better to see “sctp_connect()” than to see just “connect()” where some unseen context is what makes the compiler know that it is in the sctp module.
And you have to communicate in fragments in order to communicate efficiently.
qsqlite включает в себя sqlite. А нельзя собрать sqlite.dll отдельно и объяснить qsqlite, что у меня своя библиотека? Вроде как у них на сайте это даже и предусмотрено:If you don't want to use the SQLite library included with Qt, you can build it manually (replace $SQLITE by the directory where SQLite resides):
cd $QTDIR/src/plugins/sqldrivers/sqlite qmake "INCLUDEPATH+=$SQLITE/include" "LIBS+=-L$SQLITE/lib -lsqlite" make
<xsl:template match="url">
<xsl:template match="offer/url">
www написать:<xsl:value-of select='substring-after(., "http://heverest.ru/" )' />
<xsl:value-of select='substring-after(., "http://www.heverest.ru/")' />