Putting the 'role' back in role-playing games since 2002.
Donate to Codex
Good Old Games
  • Welcome to rpgcodex.net, a site dedicated to discussing computer based role-playing games in a free and open fashion. We're less strict than other forums, but please refer to the rules.

    "This message is awaiting moderator approval": All new users must pass through our moderation queue before they will be able to post normally. Until your account has "passed" your posts will only be visible to yourself (and moderators) until they are approved. Give us a week to get around to approving / deleting / ignoring your mundane opinion on crap before hassling us about it. Once you have passed the moderation period (think of it as a test), you will be able to post normally, just like all the other retards.

I'm getting "Base class undefined" even though I did define the bloody thing.

Joined
Jan 9, 2011
Messages
2,728
Codex 2012 Codex 2013 Codex 2014 PC RPG Website of the Year, 2015 Codex 2016 - The Age of Grimoire Make the Codex Great Again! Grab the Codex by the pussy Insert Title Here RPG Wokedex Strap Yourselves In Codex Year of the Donut Codex+ Now Streaming! Serpent in the Staglands Dead State Divinity: Original Sin Project: Eternity Torment: Tides of Numenera Wasteland 2 Codex USB, 2014 Shadorwun: Hong Kong Divinity: Original Sin 2 BattleTech Bubbles In Memoria A Beautifully Desolate Campaign Pillars of Eternity 2: Deadfire Pathfinder: Kingmaker Steve gets a Kidney but I don't even get a tag. My team has the sexiest and deadliest waifus you can recruit. Pathfinder: Wrath I'm very into cock and ball torture I helped put crap in Monomyth
What i find hilarious about current compiler thinking is that everyone recognizes that C pointer arithmetic was a mistake... for... tundumdumdum... performance reasons

I seriously can't believe anyone would say that... Any links?
 

SCO

Arcane
In My Safe Space
Joined
Feb 3, 2009
Messages
16,320
Shadorwun: Hong Kong
The lack of it permits a optimizing compiler to do whole program decisions about the underlying array that are not possible on C/++. Since a escaping int64 * can't be cast to a int32 * (for instance) it can use things like SSE instructions without having to prove it doesn't escape for AoT compilers (sometimes). For VM's it simplifies the logic of gc collections.
edit: there is even a keyword in C99 to restrict this kind of escaping:
C99 restrict keyword


I haven't got a quote, this is something i read a while ago probably on lambda the ultimate. Now that i'm looking at it it may be only the aliasing to other types of pointer. But if a future C inspired language gets rid of that they'd also get rid of arithmetic for the obvious security reasons that caused so much pain, possibly leaving only a approved 'union' type for if you really really want aliasing casts that is treated especially by the optimizer since it would be 'closed' on the types.
 

SCO

Arcane
In My Safe Space
Joined
Feb 3, 2009
Messages
16,320
Shadorwun: Hong Kong
Ok, not possible on some ancient codebases that still use casting pointers extensively. Still the warning will be a error in any new language.
 

As an Amazon Associate, rpgcodex.net earns from qualifying purchases.
Back
Top Bottom