Thanks for your reply Patrick, however, even with these suggestions the error still appears.
I tried to find out where this error is thrown and came across debug.e:
// check that tagging is supported in this file (should be a source file)
if (!_isdebugging_supported()) {
debug_message("Breakpoints are not allowed in files that are not source files.");
return(DEBUG_BREAKPOINT_NOT_ALLOWED_RC);
}
and _isdebugging_supported() has the following switch statement:
switch (dbg_get_callback_name(session_id)) {
case 'gdb':
// GDB works with other languages, and we only support C and C++
// but we can let them try to set breakpoints in those languages anyway
return(_LanguageInheritsFrom('c', lang) ||
_LanguageInheritsFrom('d', lang) ||
_LanguageInheritsFrom('f', lang) ||
_LanguageInheritsFrom('s', lang) ||
_LanguageInheritsFrom('ch', lang) ||
_LanguageInheritsFrom('asm', lang) ||
_LanguageInheritsFrom('mod', lang) ||
_LanguageInheritsFrom('ada', lang) ||
_LanguageInheritsFrom('pas'));
case 'windbg':
return(_LanguageInheritsFrom('c', lang));
case 'jdwp':
// this should work also for java embedded in HTML
return(lang=='java');
case 'xdebug':
return ( lang == 'phpscript' );
case 'pydbgp':
return ( lang == 'py' );
case 'perl5db':
return ( lang == 'pl' );
case 'rdbgp':
return ( lang == 'ruby' );
default:
// not a system we know about, revert to if taggable
return _istagging_supported(lang);
}
I set a breakpoint in the macro debugger for the 'pydbgp' case in debug.e, and then tried to set a breakpoint in the scons file.
At this point the macro debugger shows the value of lang in _isdebugging_supported() as
lang = 'fundamental'
Is there a way to tell Slickedit to report the associated language for *.scons files to be "py" instead of "fundamental"?
Just a disclaimer I don't know anything about Slick-C macro editing, but am willing to learn.