Re: [Development] Storing and managing ValueArray inside QV4::Heap objects

2018-08-20 Thread Valery Kotov
Hello Lars, > Yes, you’re right that will be problematic, as SimpleArrayData is meant to be used together with the Object it belongs to. So either use an ArrayObject, or a QVector then. I decided to give ArrayObject a try and it seems to work fine. Thank you! =) Sincerely yours, Valery Ko

Re: [Development] Storing and managing ValueArray inside QV4::Heap objects

2018-08-15 Thread Valery Kotov
ead? In case of QVector would it be safe to store JS Object pointers or it should be QVector of PersistentValues? Thank you! Sincerely yours, Valery Kotov On Thu, 9 Aug 2018 at 08:20, Valery Kotov wrote: > Hi Lars, Simon, > > I think I got it. Thanks a lot for your tips! > &g

Re: [Development] Storing and managing ValueArray inside QV4::Heap objects

2018-08-08 Thread Valery Kotov
Hi Lars, Simon, I think I got it. Thanks a lot for your tips! Sincerely yours, Valery Kotov On 8 August 2018 at 09:32, Simon Hausmann wrote: > Hi, > > > If you want to use the ValueArray, then you need to make sure that it's > the last member of your type. Then encapsulate

[Development] Storing and managing ValueArray inside QV4::Heap objects

2018-08-08 Thread Valery Kotov
s how the actually allocation for ValueArray.values is done. I suspect that it is probably not done via plain "new" call. Otherwise it is a little bit confusing why not just to store the pointer directly. Could you guys please give me a few hints how to go about ValueArray management

Re: [Development] JS Engine: callAsConstructor vs. virtualCallAsConstructor

2018-08-04 Thread Valery Kotov
it will automatically redirect to the appropriate virtualCall (re)implementation. Is that right? BR, Valery Sincerely yours, Valery Kotov On 3 August 2018 at 08:04, Lars Knoll wrote: > Hi Valery, > > On 2 Aug 2018, at 15:44, Valery Kotov wrote: > > Hello all, > > I have

[Development] JS Engine: callAsConstructor vs. virtualCallAsConstructor

2018-08-02 Thread Valery Kotov
bject *f, const Value *argv, int argc, const Value *); What is the last const Value*? Shall I pass args as last the last arguments? Sincerely yours, Valery Kotov ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

[Development] JavaScript Promise implementation, Promise.all capability-executor-not-callable test case

2018-02-08 Thread Valery Kotov
/tree/da4f4385fdf88ff2c8acf036efaaa62f8cd6bd58/test/built-ins/undefined It feels a bit like a contradiction. Thus, I'm a bit puzzled how to go about it. Am I missing something? I would appreciate some help or hints! Sincerely yours, Valery Kotov ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

[Development] Qt 5.6/dev compilation from Git

2015-09-03 Thread Valery Kotov
ng but, unfortunately, I'm a bit stuck... And, which is more unfortunate, I'm having a lack of ideas how I may handle this... Any hints or suggestions are welcomed! And thank to your support in advance! P.S. I'm sorry for sending it in 2 mailing listls... I wasn't

Re: [Development] QTBUG-36811. Qml date behaves unexpectedly for negative years.

2014-12-13 Thread Valery Kotov
Juha Varelius, Tuula Haataja Sitz der > Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB > 144331 B > > Email: ulf.herm...@theqtcompany.com | Mobile: + 49 151 68964561 | Phone: +49 > 30 63 92 3255 www.qt.io |Qt Blog: http://blog.qt.digia.com/ | Twitter: >

Re: [Development] QTBUG-36811. Qml date behaves unexpectedly for negative years.

2014-12-10 Thread Valery Kotov
opment mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development > -- Sincerely yours, Valery Kotov ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

[Development] QTBUG-36811. Qml date behaves unexpectedly for negative years.

2014-12-08 Thread Valery Kotov
ably know how qml date class should handle 0 year and negative years? Thank you! -- Sincerely yours, Valery Kotov ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] QTBUG-35892. QML XMLHttpRequest does not support the OPTIONS method.

2014-09-11 Thread Valery Kotov
roxy for HTTP/1.1 conformance. Another use case for using "OPTIONS *": preflight request in case of using CORS. -- Sincerely yours, Valery Kotov ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development