Re: [scite] Confirmation that FilePath class does not have a copy constructor

2005-10-22 Thread Neil Hodgson
April: > I think I did it because it makes more sense to change the execute > directory to that of the job being executed. I think the current loop > within SciTEBase::Execute() takes the last command's directory. For external commands on Windows, the startDirectory is copied from the jobT

Re: [scite] Confirmation that FilePath class does not have a copy constructor

2005-10-22 Thread Neil Hodgson
April: > I just want to confirm that the FilePath class does not have copy > constructor nor assignment operator. FilePath has no explicit copy constructor or assignment operator but SString has both and the only field in FilePath is an SString. Therefore, the automatically generated copy c

Re: [scite] Confirmation that FilePath class does not have a copy constructor

2005-10-22 Thread April White
April White wrote: Neil, my development of the job system ABENDS when the code is assigning the command directory in SciTEWin::ProcessExecute() dirNameForExecute = job->directory; I just realized that I moved above assignment from SciTEBase::Execute() to SciteWin::ProcessExecute(

[scite] Confirmation that FilePath class does not have a copy constructor

2005-10-22 Thread April White
Neil, my development of the job system ABENDS when the code is assigning the command directory in SciTEWin::ProcessExecute() dirNameForExecute = job->directory; I know that it is failing on this line because I've written to a log file before and after this line, the second log entry