ENIGMA Forums
Outsourcing saves money => Issues Help Desk => Topic started by: juggernaut on December 03, 2008, 01:53:06 am
-
...
Read object names.
Read room names.
Read sprite names.
Wrote resource names.
Exported object switch.
Enigma Communication Error (-1073741819)
What is causing this error?
edit: it seemed to be cause by commenting out using /* but not closing with a */
Now I am getting:
Compile failed. [1]
G++ error. Compile failed (-6)
Will look into that.
edit: I have no idea what is causing the -6 error, retroX had a similar problem but I have no variables declared not with var either..
edit: Ok the error was occurring because 2 room where named the same (I have no idea why they were though).
edit: I am now getting the -6 error again on another file and it is not the var problem or identical resource name problem this time.
edit: Ok one of the things it does not like is argument0.variable or (argument0).variable
edit: now I got an Error in No particular event for object number -3: object does not exist. Even though I had not changed anything within the objects at all before getting this error.. all I was doing was copy/pasting a piece of code within a script to a different location in the script... literally doing nothing but that and then this error occurred.
-
Source or gtfo
-
sorry can't give source I didn't save the file.
-
...
-
sorry can't give source I didn't save the file.
Yeah... no offense but that's not really helpful...
-
I didn't think. I didn't want to save the file so I could go back to a working one, I realise now I could of saved it under a different name. Sorry.
-
edit: it seemed to be cause by commenting out using /* but not closing with a */
Common sense, no?
-
>_<
I'll find the bug. Hopefully.
-
edit: it seemed to be cause by commenting out using /* but not closing with a */
Common sense, no?
Well in GM this syntax is fine.
Anyway I apologise for my uselessness.
-
Well in GM this syntax is fine.
It's a bad habit.
-
Nesting quotes is a bad habit, and you do that.
-
how is nesting quotes a bad habit? O_o
-
because it makes you recap the entire topic.
-
Why is just putting /* a bad habit? I only do it temporarily for debugging purposes.
-
Why is just putting /* a bad habit? I only do it temporarily for debugging purposes.
Use // instead
-
Why is just putting /* a bad habit? I only do it temporarily for debugging purposes.
I meant omitting */
-
Why is omitting */ a bad habit when I only to it temporarily to debug? Say there is a function in a script that ENIGMA doesn't recognise but then I want to test if another functionality is working, I will just put /* at the start of the script to comment it all out, so it will not throw an error with the function. Afterwards I will of course remove the /* and then get the script the script to work but I was just testing without it first. I do this quite a lot in GM.
-
If you want to do that, do the sneaky trick of putting "/**/" at the end of each block of code. That way, you won't get a syntax error if you put /* at the start of that piece of code...
(Matching /* and */ are in red, commented-out code is in green)
some_functional_looking_code();
/* this thing */
would be changed into
/*
some_functional_looking_code();
/* this thing */
If anyone is colour-blind, just say the word! :D
-
nesting quotes to one or two levels is not the entire topic.
and omitting */ is bad even if it's just for debugging. in anything but GM, people also use /**/ for debugging, but without the */ it won't compile.
-
nesting quotes to one or two levels is not the entire topic.
Quote nesting? Where?
-
Here.
'\''
-
Here.
'\''
Nesting≠Escaping.
-
[size=8]>_<[/size]