On 15.03.2017 11:15, Konstantin Tokarev wrote:
>
> 15.03.2017, 12:59, "Viktor Engelmann" :
>> If the program is small and you don't want it to ever grow beyond ASCII,
>> using byte arrays is okay, but in my experience, if you want to be
>> future-proof, you should interpret byte-arrays *as soon a
15.03.2017, 14:09, "Harald Vistnes" :
> So to summarize, it sounds like the recommendation is to use QString and
> QTextStream by default unless it turns out to be too slow. In that case one
> can optimize by using QByteArray or non-Qt alternatives like re2c if you have
> control over the enco
So to summarize, it sounds like the recommendation is to use QString and
QTextStream by default unless it turns out to be too slow. In that case one
can optimize by using QByteArray or non-Qt alternatives like re2c if you
have control over the encoding.
If the data read in is later put into QStrin
15.03.2017, 12:59, "Viktor Engelmann" :
> On 14.03.2017 10:50, Konstantin Tokarev wrote:
>> 14.03.2017, 12:44, "Harald Vistnes" :
>>> Hi,
>>>
>>> I'm currently working on reading and parsing large ASCII based text files
>>> and I am wondering what is the current best practice. There are so ma
On 14.03.2017 10:50, Konstantin Tokarev wrote:
>
> 14.03.2017, 12:44, "Harald Vistnes" :
>> Hi,
>>
>> I'm currently working on reading and parsing large ASCII based text files
>> and I am wondering what is the current best practice. There are so many
>> classes and macros available, so it can b
15.03.2017, 01:52, "Ch'Gans" :
> On 14 March 2017 at 22:43, Harald Vistnes wrote:
>> Hi,
>>
>> I'm currently working on reading and parsing large ASCII based text files
>> and I am wondering what is the current best practice. There are so many
>> classes and macros available, so it can be a
On 14 March 2017 at 22:43, Harald Vistnes wrote:
> Hi,
>
> I'm currently working on reading and parsing large ASCII based text files
> and I am wondering what is the current best practice. There are so many
> classes and macros available, so it can be a bit confusing to know what to
> use when.
C
On terça-feira, 14 de março de 2017 10:34:25 PDT Konstantin Tokarev wrote:
> > If you want to be flexible as to the encoding of your file, I'd use
> > QTextStream and compare to QString.
>
> Good point, but original question was about ASCII.
Which is usually good enough, until it isn't :-)
--
T
14.03.2017, 18:57, "Thiago Macieira" :
> On terça-feira, 14 de março de 2017 02:50:57 PDT Konstantin Tokarev wrote:
>> > Should I just use QString all the way, or is it faster to use some other
>> > classes when you know you don't need unicode?
>> You should use QByteArray here, which is what
On terça-feira, 14 de março de 2017 02:50:57 PDT Konstantin Tokarev wrote:
> > Should I just use QString all the way, or is it faster to use some other
> > classes when you know you don't need unicode?
> You should use QByteArray here, which is what QIODevice::readLine() returns.
> Avoid using QStr
14.03.2017, 12:44, "Harald Vistnes" :
> Hi,
>
> I'm currently working on reading and parsing large ASCII based text files and
> I am wondering what is the current best practice. There are so many classes
> and macros available, so it can be a bit confusing to know what to use when.
>
> QString,
and dont forget coming QStringView
ps. also +1 to the question
On Tue, Mar 14, 2017 at 10:43 AM, Harald Vistnes
wrote:
> Hi,
>
> I'm currently working on reading and parsing large ASCII based text files
> and I am wondering what is the current best practice. There are so many
> classes and macro
Hi,
I'm currently working on reading and parsing large ASCII based text files
and I am wondering what is the current best practice. There are so many
classes and macros available, so it can be a bit confusing to know what to
use when.
QString, QLatin1String, QByteArray, QStringLiteral, QLatin1Lit
13 matches
Mail list logo
