Metaphase

[Josh @ Dreamland]

April Fool's has finally passed, with only moderate ripple effects, I might add.

A lot of insanely awesome stuff is going on right now, a lot of which I'll keep a surprise, but I'm happy to report that Ism can now successfully pass me resource data via the DLL. We are still missing a few things that R3 had support for, which I am trying to scramble up support for. Expect a testing phase commencing tomorrow. This should not overflow into the following day.

What that test will actually look like depends on a number of factors. Right now, I'm too excited to sleep. So the project has me for a while.

LGM has a bug, seemingly only on Windows, that we'll need to isolate and resolve. Isn't a very obtrusive bug and doesn't really fall on me, so.

Other things that need done with LGM include re-implementing the syntax check button now that ENIGMA's a DLL, and configuring it to inform me of changes in the C++ resource to avoid wasting an additional second during compile.

I think I may also implement the new instance system before I begin the test phase.

Also, keep this phase relatively quiet: I'm considering making it community-members only. Two reasons for this:
1) A huge part of the point of this is to alleviate stress caused by the release having a fatal flaw that has been overlooked.
2) I want the testing phase to be a small sample of people who can actually tell me what isn't working, or what's missing.

This testing phase will hopefully be both an opportunity to debug and to request small functions, maybe systems. While you test, I will be implementing sounds. Do not expect them from day 1.

In fact, since at this point I'm getting things that were done already in R3 working, expect the entire project to be a miserable piece of failure, and then be enamored by all the wonderful things it turns out that it can do.

Of course, if it doesn't do a particular wonderful thing, such as R3.0's inability to use non-numeral-prefixed constants (such as .5), and R2's lack of comments, DO REPORT THAT.

Again, though, keep it low for now. Release should be ready by the end of tomorrow. We'll see about getting something from Luda in that. I can't stress enough not to count on all the systems that will be in R4 to be that way immediately; many of them still need integration that is better done during the testing phase. Don't expect the bitmask system yet; Luda said he'd try to have the rectangle part of his design ready, though. Also, I'm looking at backgrounds and tiles right now, frowning. So, we'll see what this gets us.

[freezway]

WOOOOOOOOHOOOOOOOOOO i wanna test!
I probably cant tell you whats happening, but i can do decent bug reprots!

[The 11th plague of Egypt]

I'm excited and afraid. I don't know if I can be really be a helpful betatester

Post made April 02, 2010, 04:52:52 am was deleted at the author's request.

[retep998]

Well then, it's time to get out the fanfare and make an announcement to the world!
Giant speakers, check.
Microphone, check.
Broadcast system which overrides every single frequency, check.
Broadcast system to override cable tv as well, check.
Speeches worldwide by many famous guest speakers, check.
Lots of bugs to smack in enigma, check.
Yup, we're all set over here.
TIME TO LAUNCH ENIGMA R4!!!

[Josh @ Dreamland]

All you have to do is post something if a piece of code won't compile. I will do my best to print helpful info about what may have went wrong, but as long as you are testing simple codes, we should get to the bottom of it relatively painlessly.

I'm just afraid a lot of things will go wrong, and there'll be reports everywhere.

@retep-

[serprex]

Fede: Glitches are preferred towards things which are more random (such as faulty hardware). Bug is the preferred term for clever code that isn't clever enough

[luiscubal]

I'd bet it doesn't support trigraphs.
I'd also bet you won't want to support trigraphs once you discover what they are.

[Josh @ Dreamland]

You're right. For unicode, short and wchar_t should be enough. I have no idea why anyone would need a third character.

[Micah]

Eh, what? Digraphs and trigraphs in C++ don't really have to do with short and wchar_t...

[Josh @ Dreamland]

Well, I'm reading that "digraphs and trigraphs are sequences of two and three characters respectively which are interpreted as one character by the programming language." That sounds just like those two to me.

[Micah]

Did you even read the Wikipedia article past the first sentence?

[Josh @ Dreamland]

No.
The implication is that they are like "#" in GML--stored like anything else, and dealt with at run.

[Rusky]

Code: [Select]

if (foo) ??<
  // ^ v those are trigraphs
??>

for (;;) <%
  /??/
  * this block has digraphs
     and this is a comment using trigraphs *??/
  /
%>

// This is all valid C++ ??/
and this is still part of the single-line comment
http://en.wikipedia.org/wiki/Digraphs_and_trigraphs#C

[Josh @ Dreamland]

Bhahahahhaha, C does those.
It warns about them, actually. You can tell it to ignore the warnings and process them.
And no, begin and end are lousy enough. Find me a really nice trigraph and I'll support it.
As in, one with a useful application that C++ wouldn't have something else for.