Click here to Skip to main content
15,302,185 members

Comments by Florian Rappl (Top 7 by date)

Florian Rappl 18-Mar-14 2:33am View
I see. Thanks for the report! I will investigate the issue and fix it as soon as possible. Please report further issues on the official page hosted on GitHub. This is just an introductory article and not the project itself.
Florian Rappl 10-Mar-14 16:58pm View
1.) Please use GitHub for such requests (where the project is located)
2.) AngleSharp is an HTML / CSS parser - it does not contain a JavaScript engine. Therefore this behavior is expected.
Florian Rappl 25-Feb-14 4:18am View
Reason for my vote of 2 \n I completely agree to johannesnestler's comment. However, I give you 2, because you have at least the words "stack" and "heap" in this tip. But I fear that there is much more and if you really want to understand memory allocations in .NET, you will have to understand memory allocations in general (I can only recommend the article by Ulrich Drepper).
Florian Rappl 18-Aug-13 7:25am View
Reason for my vote of 5 \n Good one!
Florian Rappl 24-Jul-13 11:58am View
Reason for my vote of 2 \n There is really not much in here (sorry to say). And worst of all: Send is synchronous (blocking) and therefore should not be used. Instead you should use Post, which is asynchronous. Additionally Post still works on Windows Store apps etc.
Florian Rappl 11-Jan-13 13:49pm View
Are you sure this is the problem? I highly doubt it.

An integer will never give you a null reference, since it is a struct and therefore allocated on the stack (i.e. no pointer). Even unassigned any struct will already have a value. The only way to produce this is to use a variable of type int?. This is not the case.

However, I've seen codes throwing errors on other locations. This might be the case here.
Florian Rappl 29-Aug-12 14:50pm View
Reason for my vote of 4
You did a quite good job with a really fast implementation. Your parser is well done in that direction! However, I wanted to compare your parser against one I wrote myself, and your parser had problems with more complicated strings, like

52-68^-16^5^72 -17 -89*-24*-37^24 -58

Note that this is a auto-generated equation. Anyhow: decent job!