Actor extension ability

Post a reply

Smilies
:D :) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :wink: :geek: :ugeek: :!: :?: :idea: :arrow: :| :mrgreen: :3: :wub: >:( :blergh:
View more smilies

BBCode is ON
[img] is OFF
[url] is ON
Smilies are ON

Topic review
   

Expand view Topic review: Actor extension ability

Re: Actor extension ability

by Apeirogon » Wed Jun 19, 2019 10:41 am

Graf Zahl wrote:compiler screwing things up badly
Like how, for example? Actor class, defined in gzdoom pack, definition turns into mess from code from all files?
Major Cooke wrote:Different translation units?
Roughly speaking, single zscript file is a single translation unit which gzdoom translate (turn text in it to bytecode) using magic. Different translation units -> different zscript files.
I dont know how exactly zscript compiler work, but I think it translate each file separately and then combine it into one single file, which cause conflicts between "extended" and "default" actors.

Re: Actor extension ability

by Major Cooke » Wed Jun 19, 2019 10:14 am

Different translation units?

Re: Actor extension ability

by Graf Zahl » Tue Jun 18, 2019 9:32 am

The blocker is that the compiler cannot combine parts of different translation units without screwing things up badly.

Re: Actor extension ability

by D2JK » Tue Jun 18, 2019 9:04 am

If you don't mind me asking; what stopped the progress on this feature? In a related discussion over six months ago, Graf said he was "almost done exporting PlayerPawn which is the last remaining blocker for allowing user-side extends of class Actor" (source).

Actor extension ability

by Major Cooke » Wed Jan 16, 2019 11:29 am

Just so this isn't forgotten. I understand priorities are currently elsewhere so this is just here as a reminder, seeing as Actor now has the path cleared.

Top