[DBP 7.61] Order of Type Declarations

developer forums

Bug Reports / [DBP 7.61] Order of Type Declarations

Author

Message

ShellfishGames

Years of Service

User Offline

Joined: 6th Feb 2013

Location:

Posted: 4th May 2014 15:06

Link

Not necessarily a bug, but certainly undesired behaviour:

+ Code Snippet

temp as color_type

tool_applyColor(1, temp) `<- does not work
tool_applyColor(1) `<- works

end


function tool_applyColor(tID as integer , color as color_type )
    print "Success"
endfunction

`if this type declaration happens to be set *before* the function declaration above, everything works fine
type color_type
    r as float
    g as float
    b as float
    a as float
endtype

Because color_type is declared after the tool_applyColor function and not before, that function seems to simply leave the color parameter out without any error/warning whatsoever.

It's not too unusual that a certain order of declarations is required, but the compiler really should tell me if it decides to just ignore a function's parameter.

(Tested in DBP 7.61, but as I couldn't find a single thread on the issue I just assumed it hasn't been discussed yet and thus probably hasn't been fixed in 7.7 either.. if that assumption happens to be wrong, sorry about that)

Profile PM Email Website

Green Gandalf

VIP Member

Years of Service

User Offline

Joined: 3rd Jan 2005

Playing: Malevolence:Sword of Ahkranox, Skyrim, Civ6.

Posted: 5th May 2014 23:32

Link

I agree - and in any case surely it makes more sense to give an error message on the very first line in each case since the UDT is undefined at that point?

The Help file is quite specific (although I thought you could shove them into a subroutine or am I thinking of included files?):

Quote: "To create a user defined type, you must first declare it at the top of your program."

Profile PM Email

Server time is: 2024-04-26 04:06:04
Your offset time is: 2024-04-26 04:06:04

Sorry your browser is not supported!

Bug Reports / [DBP 7.61] Order of Type Declarations