Author Topic: Compile error parsing  (Read 2691 times)

HansNet

  • Community Member
  • Posts: 8
  • Hero Points: 0
Compile error parsing
« on: October 29, 2008, 08:56:05 pm »
Hello,
I'm customizing Slickedit for editting and compiling sources that are located and compiled on a mainframe.
Here is what I(slick-c macros that call ddl-functions) do :
1. download a source-file to the pc and open a window for it in Slickedit
2. I make some changes to the source file (manual editting)
3. I have a function key, with a slick-c macro (M1) bound, to compile the source-file on the mainframe
What M1 does is the following:
- upload the source-file to the mainframe
- send a command to the mainframe to start a compile
- receive the outcome (oke or error) of the compile from the mainframe
- when outcome=error : download an error-file from the mainframe with the compile-errors in it (one or more lines with: filename;line-number;column-nr;errortekst)

I don't know how to realize the final step of the M1-macro in case of compile-error(s) :
- show the compile-errors in Slickedit
- when I click on an error goto the line/column in the source-file where the error is

Can anybody tell me how to do this ? (a simplified sample macro would be great!)

Thx.


hs2

  • Senior Community Member
  • Posts: 2734
  • Hero Points: 284
Re: Compile error parsing
« Reply #1 on: October 29, 2008, 09:13:09 pm »
Hi HansNet, is this approach not longer working for you ?
HS2

HansNet

  • Community Member
  • Posts: 8
  • Hero Points: 0
Re: Compile error parsing
« Reply #2 on: October 29, 2008, 09:52:10 pm »
Oeps ... long time ago ... I forgot all about that. I did do a search, but never got to that post.

Slickedit is becoming actual again overhere; we are now working with an editor that is no longer supported.

I have developed a VisualBasic active-X dll that does most of all functionality regarding interfacing with the mainframe. I do remember from 2007 that I couldn't directly call the active-X dll from a slick-C macro, but had to build a C++ dll (called from out of a slick-c macro) that calls the active-X dll.
Do you know if this has changed in the meantime ? (I have version 11, currently is version 13.x I read).

In VB-language I call the active-X dll as below:

    Dim objDLL As Object

    Set objDLL = CreateObject("DLL.clsDLL")
    objDLL.filename = Ucase(strFullFilename)
    objDLL.compileType = strCompileType
    objDLL.Compile
    result = objDLL.CompileResult
    if result = False then
       errorfile = objDLL.Errorfile
    end if
    Set objDLL = Nothing

hs2

  • Senior Community Member
  • Posts: 2734
  • Hero Points: 284
Re: Compile error parsing
« Reply #3 on: October 29, 2008, 10:15:04 pm »
I think the DLL interface is still the same.
Have a look here for a great example how to use a custom dll with a custom macro.
Good luck, HS2