Javascript Disabled Detected

You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality.

LaLaLa

Member Since 04 Feb 2007
Offline Last Active May 02 2012 12:07 AM

Find content

Community Stats

Group New Member
Active Posts 511
Profile Views 5949
Member Title GMC Member
Age 19 years old
Birthday November 19, 1993
Gender
Male
Location
Why do you want to know, creeper?
Interests
Programming in GML, Java, GW-BASIC, TI-BASIC, (X)HTML, CSS, JavaScript, and some PHP.
Version
GM8

15 Doing something right!

Friends

Latest Visitors

Martho
26 May 2013 - 02:49
Docopoper
08 Apr 2013 - 21:31
Yambam
09 Mar 2013 - 18:46
Overloaded
05 Mar 2013 - 12:36
sp202
07 Oct 2012 - 03:29

Posts I've Made

In Topic: 180 Degree Mouselook

01 May 2012 - 08:36 PM

There's nothing "wrong" or even relevent to your problem in the script. That works as it should. The problem is with your code that actually sets the projection of the camera, specifically, d3d_set_projection(). Post that part of you code here.

I'm assuming that you haven't taken zdirection into account when setting the up vector of the camera or something.

In Topic: Short circuit evaluation discrepency

01 May 2012 - 08:19 PM

I understand the merits of shortcut evaluation, but the problem I'm having with it is that A and B is no longer equal to B and A. I think this is confusing for non-programmers.
[...]
I don't see a quick replacement for or, but if A and B can always be replaced by if A if B.

I understand your problem with non-commutivity, but I don't see how that would be a problem when programming. If you don't pay attention to what order the comparisons are placed, then obviously short-circuit evaulation would make no difference (to a beginner, for example). But, if it is necessary, then you can purposely unitilize its effects to reduce the number of if statements (and in some cases the need for a "flag" variable to persist through the two if statements, which is what you were hinting at with short-circuit OR).

To give a clearer example, consider:

if ( !object_exists(dog) || dog.dead == true )
{
    // Make new dog or something.
}

Obviously the second comparison would fail if it was evaluated unnecessarily, when dog didn't exist. Currently you would have to do:

make_new = true;
if (object_exists(dog))
{
    if (dog.dead == false)
    {
        make_new = false;
    }
}
if (make_new == true)
{
    // Do long segment of code.
}

See? The other workaround would be to duplicate the "long segment of code". Either way, it's undesirable, and short-circuit evaluation helps.

In Topic: EncryptPass

22 April 2012 - 06:17 PM

2. The AES-128 encryption algorithm is vulnerable to a cryptological attack that would compromise it in milliseconds.

That, sir, is an asinine statement. You might want to double check you claim.

3. My product uses a custom, irreversible algorithm (adds security through obscurity).

So we should trust a custom algorithm you created rather than a well-reasoned, peer-reviewed standard like AES that has been approved for use by the NSA? Sure... Another thing, how is your algorithm "irreversible"? Even hashing functions like MD5 or Whirlpool can be broken, yet you are storing passwords that you have to be able to decrypt.

4. A cleaner user interface.

As stated by another poster, the interface is anything but "clean". It could do with some definite improvements. First, get rid of that ugly tiled background, then change that obnoxious red font for the password entry.

Having said that, I'm not here to totally bash your project. I just think it is a little unreasonable to expect people to pay money for this.