This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - Fede-lasse
cheeseboy, I'm almost flattered that you look up to me.
I feel like we should be making a pyramid.I've been out of school now for a week, and have finally been able to work on ENIGMA again. In that time, I have made some significant progress on the upgraded C parser.
Given the following input code:Code: (C++) [Select]
#include <GL/gl.h>The parse finished in 34348101 microseconds, 0 errors, 0 warnings.
#include <stdio.h> //printf, NULL
#include <stdlib.h> //malloc
#include <unistd.h> //usleep
#include <time.h> //clock
// Once affected by lack of '?' operator token
// Once affected by lack of support for public/private/protected, and by lack of support for constructors.
Pretty great, right? No. Not pretty great. That's 34 seconds, you ding-dong.
The good news is, without Valgrind (a very awesome debugger) attached, it runs a bit faster: Parse finished in 325934 microseconds.
So, about 300 milliseconds. Not bad, really. Better news is, without rendering all parsed trees to SVG files, it operates faster still:
Parse finished in 219077 microseconds.
So about 219 milliseconds. Basically happy with that? Well, if not, you can use the parser in release mode without it tossing around debug information and with optimizations turned on: Parse finished in 97204 microseconds.
Just under 100 milliseconds. Which is where I call it "Good enough." Maybe I'll do some profiling later.
Anyway, all this is pretty good news; you might be asking, where's the bad news? Bad news is, only one of those headers had any C++ in it, and that'd be pthread.h. The parser's C++ support is only just now being filled in, and I don't have a reasonably accurate ETA on that functionality. I'm thinking it'll be working sooner than later, but only time (and further work) will tell. Fortunately, only Linux users are affected by bugs in the old parser (which would probably cause parse to fail on some of the above headers).
Anyway, I'm going to get back to work. Just a heads-up, and an "I'm still alive" deal.
PS: Millisecond times are estimates, only. Given varying processors, YMMV, not to mention that times fluctuate to ±5 milliseconds even locally on consecutive runs. The release mode time actually varies from about 93 milliseconds to 102 milliseconds here.
Noone cares josh
If you can't write in the project file directory, then you can't save the project anyway. User will not write something for the project and then no save it. So temp is last resort, as in 99.9% cases this will not be a problem.Exactly, but just the fact that Ism mentions CDs makes me throw out ideas here.
I also think it should be centered. You will be able to see it just fine. The text color is either identical or very close to the link color, and you can see them just fine as well. It doesn't work well with resizing though. On my screen (1280 wide) the ticker is on top of the user info bit. If you resize the window then it also goes out of the page.Couldn't have said it better.
edit: Also, why the hell we even need that. It will only show old depressing news anyway. For example, the LGM update it boasts about right now is 2 months old. It would just give the right (sadly) impression that nothing is really happening. The date it gives is wrong though (as it shows April 4, not Feb 19).
This forum seems to attract people posting alternative programsYep.