Greetings,
Given the importance of memory management on embedded systems and to
quickly follow up on the deterministic memory manager I was referring to
earlier this year you are welcome to watch part of the following video:
https://youtu.be/vZL5X2FlZKU?t=84
You are welcome to try it out
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 now
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 says. Youtube
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
>> says. Youtube Videos are not the messias, if it’s just a w
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
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 voice that reads 1:1 what is visible on the screen? If
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* memory leaks
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
>
> Probably (1).
Ok well live long
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
Probably (1).
--
Thiago Macieira - thiago.macieira (AT) intel.com
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 stru
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 but I will first see what
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 access scope at the same
>> time.
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 access scope at the same
> time. If you give up the nested decla
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:
struct
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 following code:
temp
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 point but I personally bel
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.
> - But outside North-America and Europe, companies do not care a
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'll be at liberty to combine the
>>> first three ab
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'll be at liberty to combine the
>> first three above with whatever you like, includi
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
m
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
> mixture of:
> - Virtual reality headsets
> -
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 supporting 3D effects
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
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.
On 04/25/2018 04:46 AM, Edward Welbourne w
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
25.04.2018, 16:46, "Eric Lemanisser" :
> 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, especi
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 called across translation units. Does
yo
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
software bug can cause billion dollar proje
>> memory leaks are the most difficult problems to solve
Really NOT !
Philippe
On Wed, 25 Apr 2018 08:02:54 -0400
Phil Bouchard wrote:
> On 04/25/2018 04:46 AM, Edward Welbourne wrote:
> > Phil Bouchard (24 April 2018 19:05)
> >> Im not sure if you read the link I posted about static analysis
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
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
> >> software bug can cause billion dollar projects like space shuttles to
>
On 25.04.2018 14:02, Phil Bouchard wrote:
> You need to see the big picture; memory leaks are the most difficult
> problems to solve.
You have clearly never solved a cycle-lock.
--
Viktor Engelmann
Software Engineer
The Qt Company GmbH
Rudower Chaussee 13
D-12489 Berlin
viktor.engelm...@qt.io
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.
Th
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.
The Columbia crash wasn't a (computer) software
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...
>
> On 04/23/2018 10:34 PM, Thiago Macieira
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 Javascript in the past, so perhaps I c
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 Javascript in the past, so perhaps I can resume
> these efforts.
>
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
plagiarized
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...
On 04/23/2018 10:34 PM, Thiago Macieira wrote:
>> There are a lot of reas
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
> plagiarized quite easily.
> >>>
> >>> Ther
Hi,
În ziua de marți, 24 aprilie 2018, la 04:08:19 EEST, Phil Bouchard a scris:
> 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 crashes for apps written
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 well?
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 well?
Yes, to an extent.
> Remember
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 use any C++11 compil
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 crashes
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 crashes for apps written on the
> iPhone and fo
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 crashes for apps written on the
iPhone and for the Android as well.
- QML is an interpreted language thus it can
48 matches
Mail list logo
