Author Topic: Risks to Mixing SCI Studio and Sierra Scripts in a Project  (Read 821 times)

0 Members and 1 Guest are viewing this topic.

Offline NilG

Risks to Mixing SCI Studio and Sierra Scripts in a Project
« on: January 17, 2019, 11:36:00 AM »
The SCI Companion doc notes that:

"Both languages can be mixed and matched in the same project (but not the same file), though it is not recommended you do so (but this might be the case if you are converting an old project to the Sierra Script syntax file-by-file)."

This makes sense, and ultimately I'm shifting everything I'm gathering to Sierra Script, which is my project's overall pref/setting (been working on this with some scripts already, and even just translating from one script to the other is tightening up my grip on the syntax substantially), but it made me curious whether there are specific known risks in mixing/matching the two script types within a single project?  Do certain elements fail to work across them very well?  Or is this not recommended mainly because it just results in more muddled code than we'd want?



Offline Kawa

Re: Risks to Mixing SCI Studio and Sierra Scripts in a Project
« Reply #1 on: January 17, 2019, 01:22:46 PM »
I think it's mostly just muddle, yeah.

Offline NilG

Re: Risks to Mixing SCI Studio and Sierra Scripts in a Project
« Reply #2 on: January 18, 2019, 11:08:35 AM »
Sounds good, thanks.  I think I'll still try to avoid it, but just wanted to check if I do resort to it what to expect.


SMF 2.0.14 | SMF © 2017, Simple Machines
Simple Audio Video Embedder

Page created in 0.083 seconds with 23 queries.