Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make sdk a .use file #515

Closed
nddrylliog opened this issue Dec 25, 2012 · 5 comments
Closed

Make sdk a .use file #515

nddrylliog opened this issue Dec 25, 2012 · 5 comments
Assignees
Milestone

Comments

@nddrylliog
Copy link
Member

I thought about this:

  1. We should add Imports to .use files (yup)
  2. We should make a .use file for the sdk
  3. Rock should 'use sdk' by default in ooc files, and then people can tweak sdk.use and the sdk itself as they wish

I'll be doing it meself, no worries :)

@ghost ghost assigned nddrylliog Dec 25, 2012
@alexnask
Copy link
Collaborator

UseDef's already parse imports, are those not used?

All the rest sounds great! o/

@alexnask
Copy link
Collaborator

@nddrylliog
Just one last thing and then I'm done bothering you :P
How come you are improving the sequence driver so drastically when it is planned to be removed in 1.0?

@nddrylliog
Copy link
Member Author

@Shamanas You're not bothering me, merely distracting me :) Which is not always a bad thing.

Well, nothing prevents us from extracting the sequence driver and putting it into coke when the time has come. Since I don't know when that'll happen, in the meantime I could use faster edit/compile/run cycles when developing games, so there I go.

@nddrylliog
Copy link
Member Author

@Shamanas You're absolutely right, 1) is already done. I'll just add a guard so that we can't add imports to the module we're currently in (that's what the langImports code does, cf. this portion of code)

@nddrylliog
Copy link
Member Author

Split this issue into #524 and #525.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants