About VERGE


 
_version woes
Displaying 1-3 of 3 total.
1
Please enter a numerical value for the importance of this sticky.
Enter 0 to unsticky.
mcgrue
Okay, Jesse, looks like we gots our wires crossed. Since _version already existed, and was a string, (previously defined as 'Verge 3.0b1', the new one should be defined as a string too (already causing problems, woes!).)

We've got a suggestion of 'Verge 3.0b2 2005.07.03' so it can have the useful data in it still.

Posted on 2005-07-02 23:25:16

janus
Or perhaps just 'Verge3 YYYYMMDD' so it's easier to parse and compare.

Posted on 2005-07-02 23:29:22

Jesse
How about we let _version be some human-readable version string (which could be, for example, 'Verge3.5 - The Clam Version' and let _build be the YYYYMMDD build id as an int? That way, games could test against _build and display _version to the user?

For this release in particular, grue, I think that version string would be fine.

Posted on 2005-07-03 08:16:45


Displaying 1-3 of 3 total.
1
 
Newest messages
I Like Ham.
in Castle Heck
(by ThinIce on 2018-08-17)
Steamworks Integration
in VERGE Developers Forum
(by Eldritch05 on 2018-08-16)
Entity Issues
in VERGE Help
(by Rysen on 2018-06-05)
Epic of Serinor: Dawnshadow
in General Discussion
(by Rysen on 2018-05-13)

Ben McGraw's lovingly crafted this website from scratch for years.
It's a lot prettier this go around because of Jon Wofford.
Verge-rpg.com is a member of the lunarnet irc network, and would like to take this opportunity to remind you that regardless how babies taste, it is wrong to eat them.