a
server.
The attached examples and libarchive are perfectly stable in my testings.
Sincerely,
--
Phil Bouchard
Founder
www.fornux.com
/**
Fornux C++ Superset 2.3 -- Example.
Outputs:
Speed: 13602.559545 loops / s; Memory usage: 3936 kilobytes
*/
#include
#include
#inc
minor modifications to
the original code and it works correctly:
https://github.com/philippeb8/libarchive/commit/5858b5c047301123ffdf05f247f7d191829d5a9b
Let me know what you think!
Sincerely,
--
Phil Bouchard
Founder
p...@fornux.com
www.fornux.com
On 04/27/2018 12:22 PM, Phil Bouchard wrote:
Also I did my fair amount of contributions to science with:
- the root_ptr memory manager
- the astrophysics theory currently being peer-reviewed by the “Monthly
Notices of the Royal Astronomical Society”
Correction:
- the astrophysics theory is
Way to go Qt!
http://blog.qt.io/blog/2018/05/22/qt-for-webassembly/
I suggested this in a previous thread but apparently you already had grips
on it.
Well good job folks!
Sincerely,
-Phil
www.fornux.com
___
Development mailing list
Development@qt-pro
On 05/14/2018 06:22 AM, Konstantin Tokarev wrote:
14.05.2018, 01:45, "Phil Bouchard" :
On 05/13/2018 06:35 PM, Alexander Nassian wrote:
OMFG, besides that these are not the most difficult problems in programming,
... that computer voice that just reads what the presentation say
On 05/13/2018 06:35 PM, Alexander Nassian wrote:
OMFG, besides that these are not the most difficult problems in programming,
... that computer voice that just reads what the presentation says. Youtube
Videos are not the messias, if it’s just a written down text, publish it as
text. Why a voic
On 04/26/2018 12:35 AM, Phil Bouchard wrote:
On 04/25/2018 12:36 PM, Edward Welbourne wrote:
memory leaks are the most difficult problems to solve.
Well, no, they're not.
I've fixed *lots and lots* of memory leaks.
Some of them were a little tricky: most were trivial.
I can *see* me
Thiago Macieira wrote:
> On Wednesday, 2 May 2018 13:45:46 PDT Phil Bouchard wrote:
>> So what do you think Qt? Are you:
>>
>> 1) Not interested or whatsoever
>> 2) Interested to give a trial version a shot
>> 3) You get the idea already and might consider it
Phil Bouchard wrote:
On the other hand I am more targeting QML because QWidgets are fine already
so I assume:
- QML compiler converts QML into C++
- Fornux C++ Superset could then inject its memory manager
- Compile the resulting code
It’s just a matter of making sure QML doesn’t use nested
On 05/01/2018 09:27 AM, Phil Bouchard wrote:
Michael Corcoran wrote:
It's not really a "superset" if it doesn't support all of the features of
the original language, much less core features such as nested structs...
You may like to revisit that naming choice.
I agree
Michael Corcoran wrote:
> On 05/01/2018 11:18 AM, Phil Bouchard wrote:
>> I just tried to support nested structures and given nested structures
>> and template specializations aren't commutative then it's not possible
>> to support them if you want to respect the a
On 04/25/2018 08:02 AM, Phil Bouchard wrote:
Support for nested structures is easy to fix and will just take a day or
two to do so. For example:
struct A
{
struct B
{
};
};
Will be converted into the following so that I can have their
specialization in a top-level namespace
On 04/25/2018 11:35 PM, Phil Bouchard wrote:
template
void foo(int (&array)[N]) ?
Since I just started testing C++98 as of last week, I haven't yet had a
chance to test templates thoroughly. So this one is buggy and I'll have
to fix it.
I already fixed the problem. The
Edward Welbourne wrote:
> Phil Bouchard (27 April 2018 15:36)
>> - It’s always better to patent important algorithms
>
> Those of us who believe in the freedom of ideas disagree. It is better
> to publish important algorithms, so that no-one else can patent them.
Good poin
Edward Welbourne wrote:
> Phil Bouchard wrote:
>>>> - Fornux C++ Superset
>
> On 04/27/2018 04:18 AM, Edward Welbourne wrote:
>>> Nothing as yet persuades me that we need this one. Of course, once your
>>> compiler can handle Qt's C++ code, you
On 04/27/2018 04:18 AM, Edward Welbourne wrote:
Phil Bouchard wrote:
And I put Qt on top of the list because you already have all the
necessary layers to jump start to the next level.
Phil Bouchard (27 April 2018 00:06)
What I meant by that is Qt could create the ultimate “holodeck” with a
Phil Bouchard wrote:
> And I put Qt on top of the list because you already have all the
> necessary layers to jump start to the next level.
What I meant by that is Qt could create the ultimate “holodeck” with a
mixture of:
- Virtual reality headsets
- WebAssembly
- Qt / QML support
On 04/25/2018 12:36 PM, Edward Welbourne wrote:
memory leaks are the most difficult problems to solve.
Well, no, they're not.
I've fixed *lots and lots* of memory leaks.
Some of them were a little tricky: most were trivial.
I can *see* memory leaks just by reading code.
It's one of the reasons
On 04/25/2018 09:45 AM, Eric Lemanisser wrote:
What about
void foo(int (&array)[3])
This one works fine:
void foo(int (&array)[10])
{
cout << __PRETTY_FUNCTION__ << endl;
}
int main()
{
int array[10];
foo(array);
return 0;
}
Correctly outputs:
void foo(const boost::node_pro
Eric Lemanisser wrote:
> What about
> void foo(int (&array)[3])
> and
> template
> void foo(int (&array)[N]) ?
> Both of these functions make sure the caller and the callee use the same
> array size at compile time. I don't see anybody giving away this kind of
> security, especially fro functions
Eric Lemanisser wrote:
> Le mer. 25 avr. 2018 à 14:03, Phil Bouchard a écrit :
>
>> On 04/25/2018 04:46 AM, Edward Welbourne wrote:
>>> Phil Bouchard (24 April 2018 19:05)
>>>> I’m not sure if you read the link I posted about static analysis but a
>>&
On 04/25/2018 08:17 AM, Eric Lemanisser wrote:
Support for nested structures is easy to fix and will just take a
day or
two to do so. For example:
struct A
{
struct B
{
};
};
Will be converted into the following so that I can have their
s
On 04/25/2018 04:46 AM, Edward Welbourne wrote:
Phil Bouchard (24 April 2018 19:05)
I’m not sure if you read the link I posted about static analysis but a
software bug can cause billion dollar projects like space shuttles to fail.
Maybe MS Word was a bad example but they can be very costly
Edward Welbourne wrote:
> On Monday, 23 April 2018 18:46:05 PDT Phil Bouchard wrote:
>>>> Remember when Wordperfect kept crashing in Windows 3.1 for some strange
>>>> reason back in the days? People ended up using MS Word. The same with
>>>> Netscape
Thiago Macieira wrote:
> On Tuesday, 24 April 2018 06:13:39 PDT Phil Bouchard wrote:
>>> I can tell you right now Qt is not interested in switching languages.
>>
>> You mean switching Javascript? I already started working in a compiled
>> language to replace Javasc
On 04/24/2018 01:51 AM, Thiago Macieira wrote:
On Monday, 23 April 2018 22:35:36 PDT Phil Bouchard wrote:
On 04/23/2018 10:34 PM, Thiago Macieira wrote:
On Monday, 23 April 2018 18:46:05 PDT Phil Bouchard wrote:
- QML is an interpreted language thus it can be reverse engineered and
On 04/23/2018 10:34 PM, Thiago Macieira wrote:
On Monday, 23 April 2018 18:46:05 PDT Phil Bouchard wrote:
- QML is an interpreted language thus it can be reverse engineered and
plagiarized quite easily.
There's a QML compiler.
Which is great but does it compile the Javascript code as
On 04/23/2018 09:46 PM, Phil Bouchard wrote:
- Fornux C++ Superset harnesses the power of Clang.
Does it mean other compilers are not supported? That's a showstopper.
No it's just a Clang-based layer that injects complex C++ code into
existing C & C++98 projects. You can
On 04/23/2018 09:29 PM, Thiago Macieira wrote:
On Monday, 23 April 2018 18:08:19 PDT Phil Bouchard wrote:
Greetings,
Because Qt is very powerful, I would like to clarify the importance of
the following problems despite my previous informal attempts:
- The recent Qt 5.10.1 still randomly
handled and the memory usage never increases.
Like I mentioned previously, I am working hard on a free version I will
be able to share in a month or two.
Regards,
Phil Bouchard
www.fornux.com
/**
Fornux C++ Superset -- Example.
Outputs:
Speed: 16043.546433 loops / s; Memory usage: 4
Last call here because like I promised, here's a 17 minutes long
documentary on BB++ which now shows its internals:
https://youtu.be/GrNDYWyasxg
Regards,
-Phil
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailma
On 07/31/2017 07:12 AM, Phil Bouchard via Boost wrote:
On 07/30/2017 04:54 PM, Phil Bouchard via Boost wrote:
Like I promised, here's a 5 minutes long documentary on BB++:
https://youtu.be/vXmddU_FS30
FAQ:
"I will create a better and longer presentation this week but the go
Like I promised, here's a 5 minutes long documentary on BB++:
https://youtu.be/vXmddU_FS30
Regards,
-Phil
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
On 07/30/2017 01:23 PM, Phil Bouchard wrote:
I'll generate documentation for your convenience soon.
Like I promised, here's a 5 minutes long documentary:
https://youtu.be/vXmddU_FS30
Regards,
-Phil
___
Development mailing list
Deve
a scripting language, it will be very hard to propose anything else than
> javascript, you can try of course but without a backing company, there is
> very little chance to succeed.
>
> Best regards,
> Sylvain
>
> Le dim. 30 juil. 2017 à 19:23, Phil Bouchard a
> écrit :
&g
On 07/21/2017 12:22 AM, Phil Bouchard wrote:
Greetings,
I am now using C++14 standards, the error reporting is all compile-time
now and I get a test that is 3.5 faster than Node.JS! You can see it by
yourselves here:
https://github.com/philippeb8/root_ptr/tree/bb++/bbpp2cpp
I just tried it
Phil Bouchard wrote:
> Thiago Macieira wrote:
>>
>> Aaaand now I'm ignoring you and your arguments.
>
> I apologize; I was tired because I worked all weekend long on this. But if
> Qt can have more apps in the Apps Store or Google Play that performs 4x
> faster
On 07/26/2017 09:15 PM, Phil Bouchard wrote:
On 07/25/2017 08:11 AM, Phil Bouchard wrote:
I didn't have a chance to create documentation yesterday but I will this
week.
I just created a more complex example and it seems to be running
perfectly fine:
class Document
{
auto head = nu
On 07/25/2017 08:11 AM, Phil Bouchard wrote:
I didn't have a chance to create documentation yesterday but I will this
week.
I just created a more complex example and it seems to be running
perfectly fine:
class Document
{
auto head = nullptr();
auto tail = nullptr();
Doc
I just tried on my old Android (version 4.1.2) and the animation of the
ListView is indeed pretty bad. There is no need to try it on a recent
one since you already did.
On 07/25/2017 03:39 PM, Phil Bouchard wrote:
I'll try my example on the Android as well tonight. But it sounds like we
bindings in the delegate and not
> due to the GC.
>
> Bernhard
>
> Am Dienstag, 25. Juli 2017 schrieb Phil Bouchard :
>
>> On 07/25/2017 02:50 AM, Tomasz Siekierda wrote:
>>
>>> On 25 July 2017 at 03:09, Phil Bouchard wrote:
>>>
>>>>
On 07/25/2017 02:50 AM, Tomasz Siekierda wrote:
On 25 July 2017 at 03:09, Phil Bouchard wrote:
That's why you have to put chances on your side. Regarding the GC all you
have to do is look at the logs:
http://www.war-worlds.com/blog/2012/06/on-android-garbage-collection-can-kill-you
Thiago Macieira wrote:
> On Monday, 24 July 2017 08:15:58 PDT Phil Bouchard wrote:
>>> How do you know it wasn't some other background process waking up and
>>> doing
>>> something? Like getting the device's location and sending to the cloud? Or
>>
Thiago Macieira wrote:
> On Monday, 24 July 2017 05:47:34 PDT Phil Bouchard wrote:
>> Thiago Macieira wrote:
>>> On Sunday, 23 July 2017 15:13:50 PDT Phil Bouchard wrote:
>>> But that's just it: the GC doesn't happen as often if you're not under
>&
Phil Bouchard wrote:
> Thiago Macieira wrote:
>> But this answers the fact that you did not write a complete replacement of
>> QML.
>
> No not yet obviously. I will try to write a Youtube presentation tonight.
Actually all you have to do is include all of:
- BB++ con
Thiago Macieira wrote:
> On Sunday, 23 July 2017 15:13:50 PDT Phil Bouchard wrote:
>> On 07/23/2017 03:54 PM, Thiago Macieira wrote:
>>> A problem that can again be mitigated by adding more RAM. Sometimes it's
>>> easier/cheaper to just throw hardware a
On 07/22/2017 12:17 AM, Phil Bouchard wrote:
Greetings,
Now I have an example showing off the cyclic reference handling. Please
see:
https://github.com/philippeb8/root_ptr/blob/bb++/bbpp2cpp/tests/input2.bb
This program correctly outputs:
Document::Document(const boost::node_proxy&)
auto
On 07/23/2017 08:30 PM, Phil Bouchard wrote:
On 07/23/2017 04:34 PM, Lorn Potter wrote:
On 23/7/17 3:43 am, Phil Bouchard wrote:
Vlad Stelmahovsky wrote:
over C++ ??
No it's much faster than the Javascript -> JIT flow.
On Sat, Jul 22, 2017 at 5:43 PM, Phil Bouchard
wrote:
On 07/23/2017 04:34 PM, Lorn Potter wrote:
On 23/7/17 3:43 am, Phil Bouchard wrote:
Vlad Stelmahovsky wrote:
over C++ ??
No it's much faster than the Javascript -> JIT flow.
On Sat, Jul 22, 2017 at 5:43 PM, Phil Bouchard
wrote:
On 07/22/2017 05:52 AM, Vlad Stelmahovsky wrote
On 07/23/2017 07:12 PM, Henry Skoglund wrote:
On 2017-07-24 00:13, Phil Bouchard wrote:
On 07/23/2017 03:54 PM, Thiago Macieira wrote:
On Sunday, 23 July 2017 12:27:44 PDT Phil Bouchard wrote:
..
..
..
How does your tool deal with runtime code generation via eval() ?
First you need to ask
On 07/23/2017 05:15 PM, Thiago Macieira wrote:
On Sunday, 23 July 2017 13:02:59 PDT Phil Bouchard wrote:
On 07/23/2017 03:26 PM, Robin Burchell wrote:
Please create a bug with a test case (simple enough that it can be run
standalone like mine below) where you see more details on the
On 07/23/2017 03:54 PM, Thiago Macieira wrote:
On Sunday, 23 July 2017 12:27:44 PDT Phil Bouchard wrote:
Yes but when you have more simultaneous apps running then they will
consume more RAM thus the exact same problem will occur.
A problem that can again be mitigated by adding more RAM
On 07/23/2017 04:07 PM, Oleg Khotskin wrote:
Dunning-Kruger effect in action.
It's called: "let productive people handle it and move out of the way"
effect.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman
On 07/23/2017 03:26 PM, Robin Burchell wrote:
Please create a bug with a test case (simple enough that it can be run
standalone like mine below) where you see more details on the
performance problem you see, with information about your platform, and
full details about how you measured the result
On 07/23/2017 02:48 PM, Thiago Macieira wrote:
On Sunday, 23 July 2017 11:01:00 PDT Phil Bouchard wrote:
My experience with benchmarking very controlled and deterministic C++ code
(deterministic implies no memory allocation or deallocation) is that the
results vary on a system like that.
I am
On 07/23/2017 12:53 PM, Thiago Macieira wrote:
On Sunday, 23 July 2017 07:48:48 PDT Phil Bouchard wrote:
* You still did not provide evidence that the problems in your QML
application where due to the garbage collection.
All you have to do is create a ListView with images in the ListView
On 07/23/2017 02:50 AM, Alejandro Exojo wrote:
On Saturday 22 July 2017 18:51:28 Phil Bouchard wrote:
You're probably making a living off memory leaks so it's obvious you get
offended but I don't think being a counterproductive manager is good for
the Qt company. In fact it&#
ckberry.com>>
Sent: Saturday, July 22, 2017 11:27 AM
Subject: Re: [Development] [BB++] Now is 3.5x faster than Node.JS
To: Oleg Khotskin mailto:o.khots...@gmail.com>>,
Phil Bouchard mailto:philipp...@gmail.com>>
Cc: development mailto:development@qt-project.org>>
That'
Thiago Macieira wrote:
> On Saturday, 22 July 2017 09:22:38 PDT Phil Bouchard wrote:
>> - Replace all pointer or gc types with the 'auto' keyword in the QML parser
>> - Use standard 'operator new'
>
> You have no idea how difficult this may be. It jus
Oleg Khotskin wrote:
> Does anyone take this dumbass seriously?
>
I bet you have a better solution
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Vlad Stelmahovsky wrote:
> over C++ ??
No it's much faster than the Javascript -> JIT flow.
> On Sat, Jul 22, 2017 at 5:43 PM, Phil Bouchard wrote:
>
>> On 07/22/2017 05:52 AM, Vlad Stelmahovsky wrote:
>>
>>> Phil,
>>> Can you pleas
On 07/22/2017 12:01 PM, Giuseppe D'Angelo wrote:
On 21 July 2017 at 17:48, Phil Bouchard wrote:
For a web engine I don't think it's possible to swap the Javascript engine
entirely but it is possible to introduce the BB++ -> C++ -> WebAssembly
sequence.
For the QML / Ja
On 07/22/2017 05:52 AM, Vlad Stelmahovsky wrote:
Phil,
Can you please explain benefits of having C++ -> WebAssembly ?
Assembling speed (about 20% faster) and execution speed (about 3.5x faster):
http://webassembly.org/docs/faq/
Regards,
-Phil
___
D
Cristian Adam wrote:
> On Fri, Jul 21, 2017 at 5:48 PM, Phil Bouchard wrote:
>
>> On 07/21/2017 02:10 AM, Lorn Potter wrote:
>>
>>>
>>> On 21 Jul 2017, at 2:22 pm, Phil Bouchard wrote:
>>>>
>>>>
>>>> So I would like t
On 07/21/2017 02:10 AM, Lorn Potter wrote:
On 21 Jul 2017, at 2:22 pm, Phil Bouchard wrote:
So I would like to know if Qt thinks what I am proposing (BB++ -> C++ ->
WebAssembly) is a good plan.
What does this have to do with Qt?
For a web engine I don't think it's poss
On 07/15/2017 11:35 PM, Phil Bouchard wrote:
On 07/15/2017 01:18 PM, Phil Bouchard wrote:
On 07/15/2017 12:59 PM, Thiago Macieira wrote:
On sábado, 15 de julho de 2017 09:39:20 PDT Phil Bouchard wrote:
Yes of course, I should have anticipated that. So one option left would
be to:
- compile
On 07/15/2017 01:18 PM, Phil Bouchard wrote:
On 07/15/2017 12:59 PM, Thiago Macieira wrote:
On sábado, 15 de julho de 2017 09:39:20 PDT Phil Bouchard wrote:
Yes of course, I should have anticipated that. So one option left would
be to:
- compile the Javascript file for each architecture
On 07/15/2017 07:49 PM, Phil Bouchard wrote:
On 07/15/2017 07:21 PM, Tim Blechmann wrote:
fwiw, to get this thread back to the main topic, i still fail to see
how
root_ptr deals with objects which are reachable from multiple roots,
which have independent lifetime
Please provide an example
On 07/15/2017 09:46 PM, Phil Bouchard wrote:
On 07/15/2017 07:32 PM, Phil Bouchard wrote:
On 07/15/2017 04:58 PM, Phil Bouchard wrote:
On 07/15/2017 02:26 PM, Phil Bouchard wrote:
On 07/15/2017 02:17 PM, Tim Blechmann wrote:
fwiw, to get this thread back to the main topic, i still fail to
On 07/15/2017 07:32 PM, Phil Bouchard wrote:
On 07/15/2017 04:58 PM, Phil Bouchard wrote:
On 07/15/2017 02:26 PM, Phil Bouchard wrote:
On 07/15/2017 02:17 PM, Tim Blechmann wrote:
fwiw, to get this thread back to the main topic, i still fail to see
how
root_ptr deals with objects which are
On 07/15/2017 07:21 PM, Tim Blechmann wrote:
fwiw, to get this thread back to the main topic, i still fail to see
how
root_ptr deals with objects which are reachable from multiple roots,
which have independent lifetime
Please provide an example.
i've posted some already
I'm working on the p
On 07/15/2017 04:58 PM, Phil Bouchard wrote:
On 07/15/2017 02:26 PM, Phil Bouchard wrote:
On 07/15/2017 02:17 PM, Tim Blechmann wrote:
fwiw, to get this thread back to the main topic, i still fail to see
how
root_ptr deals with objects which are reachable from multiple roots,
which have
On 07/15/2017 02:26 PM, Phil Bouchard wrote:
On 07/15/2017 02:17 PM, Tim Blechmann wrote:
fwiw, to get this thread back to the main topic, i still fail to see
how
root_ptr deals with objects which are reachable from multiple roots,
which have independent lifetime
Please provide an example
On 07/15/2017 02:17 PM, Tim Blechmann wrote:
fwiw, to get this thread back to the main topic, i still fail to see how
root_ptr deals with objects which are reachable from multiple roots,
which have independent lifetime
Please provide an example.
i've posted some already
I'm working on the p
On 07/15/2017 01:34 PM, Tim Blechmann wrote:
Oh sorry they did invent Minesweeper and Basic, I give them that...
https://en.wikipedia.org/wiki/Dartmouth_BASIC
Lol.
fwiw, to get this thread back to the main topic, i still fail to see how
root_ptr deals with objects which are reachable from m
On 07/15/2017 12:59 PM, Thiago Macieira wrote:
On sábado, 15 de julho de 2017 09:39:20 PDT Phil Bouchard wrote:
Yes of course, I should have anticipated that. So one option left would
be to:
- compile the Javascript file for each architecture / platform
- link that "jex" to a portab
On 07/15/2017 02:56 AM, Thiago Macieira wrote:
On sexta-feira, 14 de julho de 2017 12:13:52 PDT Phil Bouchard wrote:
[1] https://clearlinux.org/features/intel%C2%AE-clear-containers
I understand but what's the problem with containers? I think Linux
containers are also supported under Wi
On 07/14/2017 12:58 AM, Phil Bouchard wrote:
On 07/13/2017 10:32 AM, Grégoire Barbier wrote:
Le 13/07/2017 à 14:33, Phil Bouchard a écrit :
Sérgio Martins wrote:
On Thu, Jul 13, 2017 at 4:54 AM, Phil Bouchard
wrote:
Anyway I'm deviating from QNodePtr but I just don't understan
Thiago Macieira wrote:
> On sexta-feira, 14 de julho de 2017 10:08:13 PDT Phil Bouchard wrote:
>>> Please read up a little on a subject before you make such an outlandish
>>> suggestion.
>>
>> Yes sorry that was just a quick guess but in Linux you can run Linu
Thiago Macieira wrote:
> On sexta-feira, 14 de julho de 2017 05:06:14 PDT Phil Bouchard wrote:
>>> Except for the fact that no browser would ever download and execute
>>> untrusted binaries like that.
>>>
>>> The closest is Native Client (NaCl).
>>
&
On 07/14/2017 03:18 AM, Thiago Macieira wrote:
On quinta-feira, 13 de julho de 2017 17:32:58 PDT Phil Bouchard wrote:
You just helped me figure something out: people want speed, right?
- You offer a service which converts and compiles all Javascript files
for most popular architectures (i386
On 07/13/2017 10:32 AM, Grégoire Barbier wrote:
Le 13/07/2017 à 14:33, Phil Bouchard a écrit :
Sérgio Martins wrote:
On Thu, Jul 13, 2017 at 4:54 AM, Phil Bouchard
wrote:
Anyway I'm deviating from QNodePtr but I just don't understand the hype
about JIT when it doesn't s
On 07/13/2017 10:32 AM, Grégoire Barbier wrote:
Le 13/07/2017 à 14:33, Phil Bouchard a écrit :
I'm working on it; it shouldn't take too long.
<3
« I have discovered a truly marvelous proof of this, which this margin
is too narrow to contain. »
Pierre de Fermat, 1637 A.D.
Took
On 07/13/2017 01:20 PM, André Pönitz wrote:
On Wed, Jul 12, 2017 at 11:54:54PM -0400, Phil Bouchard wrote:
On 07/12/2017 10:28 PM, Thiago Macieira wrote:
On quarta-feira, 12 de julho de 2017 12:34:35 PDT Phil Bouchard wrote:
I don't know about you but a minimalist version of g++ emb
André Pönitz wrote:
> On Wed, Jul 12, 2017 at 11:54:54PM -0400, Phil Bouchard wrote:
> On 07/12/2017 10:28 PM, Thiago Macieira wrote:
> >On quarta-feira, 12 de julho de 2017 12:34:35 PDT Phil Bouchard wrote:
> >>I don't know about you but a minimalist version
Grégoire Barbier wrote:
> Le 13/07/2017 à 14:33, Phil Bouchard a écrit :
> Sérgio Martins wrote:
>> On Thu, Jul 13, 2017 at 4:54 AM, Phil Bouchard wrote:
>>> Anyway I'm deviating from QNodePtr but I just don't understand the hype
>>> about JIT when i
Sérgio Martins wrote:
> On Thu, Jul 13, 2017 at 4:54 AM, Phil Bouchard wrote:
>> Anyway I'm deviating from QNodePtr but I just don't understand the hype
>> about JIT when it doesn't seem it has been compared to a Javascript compiler
>> because none exists
On 07/13/2017 04:09 AM, Konstantin Tokarev wrote:
13.07.2017, 02:39, "Phil Bouchard" :
On 07/12/2017 07:25 PM, Phil Bouchard wrote:
On 07/12/2017 04:56 PM, Konstantin Tokarev wrote:
Now add time of compilation to the sum
So I just did benchmark the following C++ file featur
On 07/13/2017 12:13 AM, Thiago Macieira wrote:
Third, only 1.8 times faster? That's actually a very impressive JIT. I'd have
expected a much worse number.
Yes but the longer the loop lasts in the example, the greater the
difference is between the executable and Node.JS. The "speed slope" is
On 07/12/2017 10:28 PM, Thiago Macieira wrote:
On quarta-feira, 12 de julho de 2017 12:34:35 PDT Phil Bouchard wrote:
I don't know about you but a minimalist version of g++ embedded inside the
browser could be beneficial big time.
Such a thing exists, it's called JIT.
I was readin
On 07/12/2017 07:25 PM, Phil Bouchard wrote:
And the executable generated by g++ is still 1.7 times faster than by
using Node.JS.
Make that 1.8 times faster when using a main precompiled header.
___
Development mailing list
Development@qt
On 07/12/2017 07:25 PM, Phil Bouchard wrote:
On 07/12/2017 04:56 PM, Konstantin Tokarev wrote:
Now add time of compilation to the sum
So I just did benchmark the following C++ file featuring a loop within
the code (the loop was at the bash shell level previously):
https://github.com
On 07/12/2017 10:58 AM, Phil Bouchard wrote:
Phil Bouchard wrote:
On 07/11/2017 04:02 AM, Tim Blechmann wrote:
On the other hand, I have good news as I think I have found a way to
simulate functions that return a function.
how to you cope with structures like:
function foo( outObject
On 07/12/2017 04:56 PM, Konstantin Tokarev wrote:
12.07.2017, 22:35, "Phil Bouchard" :
Phil Bouchard wrote:
On 07/11/2017 06:36 AM, Konstantin Tokarev wrote:
10.07.2017, 21:56, "Phil Bouchard" :
Phil Bouchard wrote:
BTW converting Javascript into C++ seems very e
Phil Bouchard wrote:
> On 07/11/2017 06:36 AM, Konstantin Tokarev wrote:
>>
>>
>> 10.07.2017, 21:56, "Phil Bouchard" :
>>> Phil Bouchard wrote:
>>>> BTW converting Javascript into C++ seems very easy to do
>>>
>>> In fact
Phil Bouchard wrote:
> On 07/11/2017 04:02 AM, Tim Blechmann wrote:
>>> On the other hand, I have good news as I think I have found a way to
>>> simulate functions that return a function.
>>
>> how to you cope with structures like:
>>
>>
On 07/11/2017 06:36 AM, Konstantin Tokarev wrote:
10.07.2017, 21:56, "Phil Bouchard" :
Phil Bouchard wrote:
BTW converting Javascript into C++ seems very easy to do
In fact, is it me or it would seem that:
- converting the Javascript code into C++ on-the-fly
- compiling the r
On 07/11/2017 04:02 AM, Tim Blechmann wrote:
On the other hand, I have good news as I think I have found a way to
simulate functions that return a function.
how to you cope with structures like:
function foo( outObject )
{
var object = {}
outObject.object = object
outObject.result
ould be that bar was initialized to "100", in which case I think an
> exception would be thrown at the attempt of calling it.
>
>
> Simon
>
>
> From: Development
> on behalf of Phil
> Bouchard
>
> Sent: Tuesday, July 11
On 07/11/2017 04:02 AM, Tim Blechmann wrote:
On the other hand, I have good news as I think I have found a way to
simulate functions that return a function.
how to you cope with structures like:
function foo( outObject )
{
var object = {}
outObject.object = object
outObject.result
1 - 100 of 155 matches
Mail list logo
