• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
TheAtom

shared issues

6 posts in this topic

Tested with AS rev 1176 (and can't see anything about fixing these in the commitlog).

1. The following gives "Can't return value when return type is 'void'." upon compilation:
[code]
shared int f()
{
return 0;
}
[/code]

2. imported functions are always considered non-shared and thus are unusable in any shared code. Perhaps imported functions should be always treated as shared, or maybe it could be done explicitly:
[code]
import shared int f() from "module";
[/code]
0

Share this post


Link to post
Share on other sites
Thanks. I fixed this bug now, in revision 1262.


Imported functions are not 'shared'. This is because the imported functions are dynamically linked individually per module. Imported functions will also access the global variables in the originating module. To be 'shared' the function (or other entity) cannot have any module specific behaviour.

It is possible to import a function that is shared by another module, but then you hide the fact that the function is shared.
0

Share this post


Link to post
Share on other sites
What would be wrong with checking if an imported function used by a shared code is shared upon bind time, and giving a bind error if it isn't?
[code]
// module mod1
shared void f1() { }
void f2() { }

// module mod2
import void f1() from "mod1";
import void f2() from "mod1";
shared void g()
{
f1();
f2(); // bind error on this one when BindAllImportedFunctions()
}
[/code]
0

Share this post


Link to post
Share on other sites
The actual bind id is still module specific, so the function g() cannot be compiled in a module independent way.

What exactly are you trying to accomplish? Perhaps there is an easier way. If the function already is shared, then there is not really any need to import it. Simply declare it again as shared, and it will be the same function.
0

Share this post


Link to post
Share on other sites
I have a few large modules that serve as a general API for every scripted ingame feature, coupled with a header script for each one of them that is nothing more than a wall of imports (plus macros and interfaces used). Then, I have some utility classes inlined in several modules (I'd like them to be shared for that reason) that use those headers. While I could simply put the function bodies in said headers to make it work, it is not an option: our headers are readily available to a larger group of people who do not have the access to the modules themselves, for security reasons (at best they receive them in a binary form; but generally they can only send new scripts to an isolated testing environment and run stuff remotely). Of a lesser importance is that the code would be somewhat uglier.
0

Share this post


Link to post
Share on other sites
I think in this case you can take advantage of an undocumented feature: A shared function is not re-compiled if it finds a pre-existing function from another module. The same goes for classes, interfaces, and enums.

Using this you can can declare the shared function with an empty body in the header that you distribute to your clients. The main module will provide the true implementation.

[code]
shared int f() {}
shared class c {}
shared interface i {}
shared enum e {}
[/code]

You just need to make sure the large module that has the real function implementation is always compiled before any other modules that will only have the empty function, class, interface, or enum.
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0