|
View:
New views
4 Messages
—
Rating Filter:
Alert me
|
|
|
2980 caused breaking change in CompilerParameters.csTraceSwitch no longer being publicly accessible in CompilerParameters.cs appears to have broken BooBinding in SharpDevelop. Can it be made public again? Error parsing a_file.boo Exception thrown: System.MissingFieldException: Field not found: 'Boo.Lang.Compiler.CompilerParameters.TraceSwitch'. at Grunwald.BooBinding.CodeCompletion.BooParser.Parse(IProjectContent projectContent, String fileName, Int32[] lineLength, BooCompiler compiler) at Grunwald.BooBinding.CodeCompletion.BooParser.Parse(IProjectContent projectContent, String fileName, String fileContent) at ICSharpCode.SharpDevelop.ParserService.ParseFile(IProjectContent fileProjectContent, String fileName, String fileContent, Boolean updateCommentTags) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Boo Programming Language" group. To post to this group, send email to boolang@... To unsubscribe from this group, send email to boolang-unsubscribe@... For more options, visit this group at http://groups.google.com/group/boolang -~----------~----~----~----~------~----~------~--~--- |
|
|
Re: 2980 caused breaking change in CompilerParameters.csI tried making TraceSwitch public, but it made no difference. So should this be considered a Boo issue or a SharpDevelop issue? On Mon, Jul 7, 2008 at 3:00 PM, sprucely <timberdig@...> wrote: > > TraceSwitch no longer being publicly accessible in > CompilerParameters.cs appears to have broken BooBinding in > SharpDevelop. Can it be made public again? > > Error parsing a_file.boo > Exception thrown: > System.MissingFieldException: Field not found: > 'Boo.Lang.Compiler.CompilerParameters.TraceSwitch'. > at > Grunwald.BooBinding.CodeCompletion.BooParser.Parse(IProjectContent > projectContent, String fileName, Int32[] lineLength, BooCompiler > compiler) > at > Grunwald.BooBinding.CodeCompletion.BooParser.Parse(IProjectContent > projectContent, String fileName, String fileContent) > at ICSharpCode.SharpDevelop.ParserService.ParseFile(IProjectContent > fileProjectContent, String fileName, String fileContent, Boolean > updateCommentTags) > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Boo Programming Language" group. To post to this group, send email to boolang@... To unsubscribe from this group, send email to boolang-unsubscribe@... For more options, visit this group at http://groups.google.com/group/boolang -~----------~----~----~----~------~----~------~--~--- |
|
|
Re: 2980 caused breaking change in CompilerParameters.csOn Tue, Jul 8, 2008 at 1:45 PM, Spruce Weber <timberdig@...> wrote: > > I tried making TraceSwitch public, but it made no difference. So > should this be considered a Boo issue or a SharpDevelop issue? > I think the way to go might be to make a new release to consolidate the API change and have the new release adopted by #develop. Daniel, what do you think? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Boo Programming Language" group. To post to this group, send email to boolang@... To unsubscribe from this group, send email to boolang-unsubscribe@... For more options, visit this group at http://groups.google.com/group/boolang -~----------~----~----~----~------~----~------~--~--- |
|
|
Re: 2980 caused breaking change in CompilerParameters.csI noticed this one a while ago, but it seems like it'd be easier to change #D. I made a post on their forums, but I guess it was too technical to get any notice. http://community.sharpdevelop.net/forums/t/7873.aspx All the fix requires is commenting out one line in the plugin. On Jul 8, 11:32 am, "Rodrigo B. de Oliveira" <rodrigobam...@...> wrote: > On Tue, Jul 8, 2008 at 1:45 PM, Spruce Weber <timber...@...> wrote: > > > I tried making TraceSwitch public, but it made no difference. So > > should this be considered a Boo issue or a SharpDevelop issue? > > I think the way to go might be to make a new release to consolidate > the API change and have the new release adopted by #develop. Daniel, > what do you think? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Boo Programming Language" group. To post to this group, send email to boolang@... To unsubscribe from this group, send email to boolang-unsubscribe@... For more options, visit this group at http://groups.google.com/group/boolang -~----------~----~----~----~------~----~------~--~--- |
| Free Forum Powered by Nabble | Forum Help |