Skip to content
This repository has been archived by the owner on Sep 24, 2019. It is now read-only.

Fix --no-preserve option when compiling KAMs #34

Open
abargnesi opened this issue Jul 31, 2012 · 1 comment
Open

Fix --no-preserve option when compiling KAMs #34

abargnesi opened this issue Jul 31, 2012 · 1 comment
Labels
ready for testing
Milestone
2.0.1

Comments

@abargnesi
Copy link
Member

The --no-preserve option should tell the BEL Compiler to overwrite a KAM by the same name of the one your compiling. We have always said that the default was to not preserve KAMs, but this option was never implemented for the BEL Compiler.

Implement the "--no-preserve" option. The default, when option is not specified, should be to preserve the existing KAM from being overwritten. If the user specifies the "--no-preserve" option then the the BEL Compiler should be allowed to continue compiling and eventually overwrite the KAM.
@ghost ghost assigned jhourani Jul 31, 2012
nbargnesi pushed a commit that referenced this issue Aug 7, 2012
Merge pull request #36 from jhourani/experimental
1f0ebb9 
Fixes issue #34, implements --no-preserve.
@jhourani
Copy link

jhourani commented Aug 9, 2012

Look at closing this issue.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
ready for testing
Projects
None yet
Milestone
2.0.1
Development

No branches or pull requests
2 participants
@abargnesi @jhourani