{"title":"避免与面向方面编程中的异常处理混淆","authors":"Ismael Figueroa","doi":"10.1145/1960314.1960345","DOIUrl":null,"url":null,"abstract":"Exception-related aspects may inadvertently alter the exception flow paths in a program: a base handler may capture an exception thrown by advice, as seen in Figure 1(a). Also the dual situation can occur, as shown in Figure 1(b). Listing 1 shows the AspectJ code associated to the problem shown in Figure 1(a): method foo calls getConfiguration to obtain a configuration parameter. foo installs a handler to set a default value","PeriodicalId":353153,"journal":{"name":"Aspect-Oriented Software Development","volume":"22 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2011-03-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"2","resultStr":"{\"title\":\"Avoiding confusion with exception handling in aspect-oriented programming\",\"authors\":\"Ismael Figueroa\",\"doi\":\"10.1145/1960314.1960345\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Exception-related aspects may inadvertently alter the exception flow paths in a program: a base handler may capture an exception thrown by advice, as seen in Figure 1(a). Also the dual situation can occur, as shown in Figure 1(b). Listing 1 shows the AspectJ code associated to the problem shown in Figure 1(a): method foo calls getConfiguration to obtain a configuration parameter. foo installs a handler to set a default value\",\"PeriodicalId\":353153,\"journal\":{\"name\":\"Aspect-Oriented Software Development\",\"volume\":\"22 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2011-03-21\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"2\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"Aspect-Oriented Software Development\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1145/1960314.1960345\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"Aspect-Oriented Software Development","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1145/1960314.1960345","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Avoiding confusion with exception handling in aspect-oriented programming
Exception-related aspects may inadvertently alter the exception flow paths in a program: a base handler may capture an exception thrown by advice, as seen in Figure 1(a). Also the dual situation can occur, as shown in Figure 1(b). Listing 1 shows the AspectJ code associated to the problem shown in Figure 1(a): method foo calls getConfiguration to obtain a configuration parameter. foo installs a handler to set a default value