Bareword found where operator expected at (eval 101) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 101) line 34, near "--82" (Missing operator before 82?) Graham, Bareword found where operator expected at (eval 103) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 103) line 34, near "--82" (Missing operator before 82?) Thanks for your response. I took a look at your syntax and here is Bareword found where operator expected at (eval 105) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 105) line 34, near "--82" (Missing operator before 82?) what I found. Bareword found where operator expected at (eval 107) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 107) line 34, near "--82" (Missing operator before 82?) Bareword found where operator expected at (eval 109) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 109) line 34, near "--82" (Missing operator before 82?) It still appears that an event trigger (->) is not allowed in an analog Bareword found where operator expected at (eval 111) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 111) line 34, near "--82" (Missing operator before 82?) block. Bareword found where operator expected at (eval 113) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 113) line 34, near "--82" (Missing operator before 82?) Bareword found where operator expected at (eval 115) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 115) line 34, near "--82" (Missing operator before 82?) I noticed that when declaring named events that they can be declared Bareword found where operator expected at (eval 117) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 117) line 34, near "--82" (Missing operator before 82?) with dimensions, but that the syntax for the event control statements do Bareword found where operator expected at (eval 118) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 118) line 34, near "--82" (Missing operator before 82?) not support specifying the dimension. Bareword found where operator expected at (eval 119) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 119) line 34, near "--82" (Missing operator before 82?) Bareword found where operator expected at (eval 120) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 120) line 34, near "--82" (Missing operator before 82?) Finally, I noticed that @* and @(*) are valid event control statements Bareword found where operator expected at (eval 121) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 121) line 34, near "--82" (Missing operator before 82?) in the digital context but not in the analog. I have no idea what they Bareword found where operator expected at (eval 122) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 122) line 34, near "--82" (Missing operator before 82?) mean, but I thought I would point out the inconsistency. Bareword found where operator expected at (eval 123) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 123) line 34, near "--82" (Missing operator before 82?) Bareword found where operator expected at (eval 124) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 124) line 34, near "--82" (Missing operator before 82?) -Ken Bareword found where operator expected at (eval 125) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 125) line 34, near "--82" (Missing operator before 82?) Bareword found where operator expected at (eval 126) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 126) line 34, near "--82" (Missing operator before 82?) Graham Helwig wrote: Bareword found where operator expected at (eval 127) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 127) line 34, near "--82" (Missing operator before 82?) > Hello Ken, Bareword found where operator expected at (eval 128) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 128) line 34, near "--82" (Missing operator before 82?) > Bareword found where operator expected at (eval 129) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 129) line 34, near "--82" (Missing operator before 82?) > Please see my comments below: Bareword found where operator expected at (eval 130) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 130) line 34, near "--82" (Missing operator before 82?) > Bareword found where operator expected at (eval 131) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 131) line 34, near "--82" (Missing operator before 82?) >> 1. In the 2.2 LRM the event_control syntax definition seems ambiguous. Bareword found where operator expected at (eval 132) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 132) line 34, near "--82" (Missing operator before 82?) >> The event_control statement is defined in terms of an Bareword found where operator expected at (eval 133) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 133) line 34, near "--82" (Missing operator before 82?) >> event_expression, but an event_expression is never defined. Rather Bareword found where operator expected at (eval 134) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 134) line 34, near "--82" (Missing operator before 82?) >> analog_event_expression and digital_event_expressions are defined, Bareword found where operator expected at (eval 135) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 135) line 34, near "--82" (Missing operator before 82?) >> but it is never made clear how they relate to an event_expression. Bareword found where operator expected at (eval 136) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 136) line 34, near "--82" (Missing operator before 82?) >> 2. It does not appear as if one can trigger a named event within an Bareword found where operator expected at (eval 137) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 137) line 34, near "--82" (Missing operator before 82?) >> analog block (the -> operator is not mentioned in the 2.2 LRM from Bareword found where operator expected at (eval 138) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 138) line 34, near "--82" (Missing operator before 82?) >> what I can tell). Bareword found where operator expected at (eval 139) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 139) line 34, near "--82" (Missing operator before 82?) >> Bareword found where operator expected at (eval 140) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 140) line 34, near "--82" (Missing operator before 82?) > Bareword found where operator expected at (eval 141) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 141) line 34, near "--82" (Missing operator before 82?) > I'm aware of a number of these event expression related problems in LRM Bareword found where operator expected at (eval 142) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 142) line 34, near "--82" (Missing operator before 82?) > 2.2. Have a look at the event expression syntax of Bareword found where operator expected at (eval 143) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 143) line 34, near "--82" (Missing operator before 82?) > http://www.verilog.org/verilog-ams/htmlpages/public-docs/merged_syntax.pdf. Bareword found where operator expected at (eval 144) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 144) line 34, near "--82" (Missing operator before 82?) > Does this address your needs? Bareword found where operator expected at (eval 145) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 145) line 34, near "--82" (Missing operator before 82?) > Bareword found where operator expected at (eval 146) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 146) line 34, near "--82" (Missing operator before 82?) >> 3. A change in an analog discrete variable (an integer) cannot trigger Bareword found where operator expected at (eval 147) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 147) line 34, near "--82" (Missing operator before 82?) >> a change in a continuous assignment nor in an event expression. Bareword found where operator expected at (eval 148) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 148) line 34, near "--82" (Missing operator before 82?) >> (This is ambiguous in the LRM and not allowed in the Cadence Bareword found where operator expected at (eval 149) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 149) line 34, near "--82" (Missing operator before 82?) >> implementation.) Bareword found where operator expected at (eval 150) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 150) line 34, near "--82" (Missing operator before 82?) >> Bareword found where operator expected at (eval 151) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 151) line 34, near "--82" (Missing operator before 82?) > Bareword found where operator expected at (eval 152) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 152) line 34, near "--82" (Missing operator before 82?) > Agreed, it would be help for continuous assignment statements to be Bareword found where operator expected at (eval 153) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 153) line 34, near "--82" (Missing operator before 82?) > sensitive to discrete integer variables. IF this is to be allowed then Bareword found where operator expected at (eval 154) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 154) line 34, near "--82" (Missing operator before 82?) > it should be document in section 6. Bareword found where operator expected at (eval 155) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 155) line 34, near "--82" (Missing operator before 82?) > Bareword found where operator expected at (eval 156) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 156) line 34, near "--82" (Missing operator before 82?) >> Note, between restrictions 2 & 3, it is not possible to have analog Bareword found where operator expected at (eval 157) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 157) line 34, near "--82" (Missing operator before 82?) >> behavior trigger changes in digital signals without there being a cross Bareword found where operator expected at (eval 158) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 158) line 34, near "--82" (Missing operator before 82?) >> function involved, and and one cannot use cross functions on integers. Bareword found where operator expected at (eval 159) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 159) line 34, near "--82" (Missing operator before 82?) >> Bareword found where operator expected at (eval 160) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 160) line 34, near "--82" (Missing operator before 82?) >> 4. Cannot have multiple analog blocks. This unnecessary restriction Bareword found where operator expected at (eval 161) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 161) line 34, near "--82" (Missing operator before 82?) >> forces dissimilar behavior to be combined into a single block, Bareword found where operator expected at (eval 162) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 162) line 34, near "--82" (Missing operator before 82?) >> which is unlike the original Verilog language. It also limits Bareword found where operator expected at (eval 163) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 163) line 34, near "--82" (Missing operator before 82?) >> the language support for multirate simulation techniques. Bareword found where operator expected at (eval 164) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 164) line 34, near "--82" (Missing operator before 82?) >> Bareword found where operator expected at (eval 165) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 165) line 34, near "--82" (Missing operator before 82?) > Bareword found where operator expected at (eval 166) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 166) line 34, near "--82" (Missing operator before 82?) > Agreed multiple analog blocks would be useful to better organize the Bareword found where operator expected at (eval 167) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 167) line 34, near "--82" (Missing operator before 82?) > contents of a large mixed-signal module to be more modular instead of Bareword found where operator expected at (eval 168) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 168) line 34, near "--82" (Missing operator before 82?) > lumping the analog behavior together (away from it related digital Bareword found where operator expected at (eval 169) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 169) line 34, near "--82" (Missing operator before 82?) > blocks) in one part of a module description. Bareword found where operator expected at (eval 170) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 170) line 34, near "--82" (Missing operator before 82?) > Bareword found where operator expected at (eval 171) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 171) line 34, near "--82" (Missing operator before 82?) >> 5. At some point I remember there being a restriction that a node Bareword found where operator expected at (eval 172) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 172) line 34, near "--82" (Missing operator before 82?) >> declared as being ground could not be the first node listed in Bareword found where operator expected at (eval 173) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 173) line 34, near "--82" (Missing operator before 82?) >> an access function, but I cannot find that restriction in the Bareword found where operator expected at (eval 174) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 174) line 34, near "--82" (Missing operator before 82?) >> v2.2 LRM. Is that still a restriction? If so it should be removed Bareword found where operator expected at (eval 175) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 175) line 34, near "--82" (Missing operator before 82?) >> as it means that the behavior must be written knowing which node Bareword found where operator expected at (eval 176) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 176) line 34, near "--82" (Missing operator before 82?) >> is ground, making it more difficult to copy and paste code fragments. Bareword found where operator expected at (eval 177) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 177) line 34, near "--82" (Missing operator before 82?) >> Bareword found where operator expected at (eval 178) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 178) line 34, near "--82" (Missing operator before 82?) > Bareword found where operator expected at (eval 179) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 179) line 34, near "--82" (Missing operator before 82?) > Yes, I believe it has been removed. Currently nothing is documented Bareword found where operator expected at (eval 180) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 180) line 34, near "--82" (Missing operator before 82?) > about ground terminals. I figure it was good to add a short statement Bareword found where operator expected at (eval 181) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 181) line 34, near "--82" (Missing operator before 82?) > to the affect that ground nets are treated no different to non-ground Bareword found where operator expected at (eval 182) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 182) line 34, near "--82" (Missing operator before 82?) > nets when used as branch terminals. Bareword found where operator expected at (eval 183) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 183) line 34, near "--82" (Missing operator before 82?) > Bareword found where operator expected at (eval 184) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 184) line 34, near "--82" (Missing operator before 82?) >> 6. It would be nice to have real valued variables act as registers. Bareword found where operator expected at (eval 185) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 185) line 34, near "--82" (Missing operator before 82?) >> In other words, it would be nice if reals could act as ports without Bareword found where operator expected at (eval 186) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 186) line 34, near "--82" (Missing operator before 82?) >> needing a continuous assignment to a wreal. In this way real becomes Bareword found where operator expected at (eval 187) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 187) line 34, near "--82" (Missing operator before 82?) >> something like a 64 bit register with implied $realtobits() and Bareword found where operator expected at (eval 188) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 188) line 34, near "--82" (Missing operator before 82?) >> $bitstoreal() conversions, with the difference being that you could Bareword found where operator expected at (eval 189) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 189) line 34, near "--82" (Missing operator before 82?) >> use a scalar wire to connect to the port. It would be important Bareword found where operator expected at (eval 190) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 190) line 34, near "--82" (Missing operator before 82?) >> to pass this enhancement back to verilog itself, along with the Bareword found where operator expected at (eval 191) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 191) line 34, near "--82" (Missing operator before 82?) >> need for a wreal, as this represents an large issue when trying Bareword found where operator expected at (eval 192) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 192) line 34, near "--82" (Missing operator before 82?) >> to use Verilog-AMS to develop pure verilog models of analog IP. Bareword found where operator expected at (eval 193) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 193) line 34, near "--82" (Missing operator before 82?) >> To develop a pin accurate verilog model of analog IP you need to Bareword found where operator expected at (eval 194) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 194) line 34, near "--82" (Missing operator before 82?) >> have a simple scalar pin for each bias line (vdd, vss, etc.), Bareword found where operator expected at (eval 195) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 195) line 34, near "--82" (Missing operator before 82?) >> and that pin needs to pass a real value. Today you cannot do Bareword found where operator expected at (eval 196) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 196) line 34, near "--82" (Missing operator before 82?) >> this with verilog, you need a 64bit buss, meaning that the model Bareword found where operator expected at (eval 197) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 197) line 34, near "--82" (Missing operator before 82?) >> is no longer pin accurate. Bareword found where operator expected at (eval 198) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 198) line 34, near "--82" (Missing operator before 82?) >> Bareword found where operator expected at (eval 199) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 199) line 34, near "--82" (Missing operator before 82?) > Bareword found where operator expected at (eval 200) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 200) line 34, near "--82" (Missing operator before 82?) > I would also include connectmodules with a wreal digital port need to be Bareword found where operator expected at (eval 201) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 201) line 34, near "--82" (Missing operator before 82?) > considered. OK, connectmodule don't support vector digital ports, and Bareword found where operator expected at (eval 202) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 202) line 34, near "--82" (Missing operator before 82?) > wreal is treated as a 64-bit vector. The difference is that the wreal Bareword found where operator expected at (eval 203) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 203) line 34, near "--82" (Missing operator before 82?) > vector is always treated as a scalar. Bareword found where operator expected at (eval 204) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 204) line 34, near "--82" (Missing operator before 82?) > Bareword found where operator expected at (eval 205) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 205) line 34, near "--82" (Missing operator before 82?) >> 7. Cadence's implementation does not support transition sensitivity of Bareword found where operator expected at (eval 206) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 206) line 34, near "--82" (Missing operator before 82?) >> a digital register in an analog block. Thus, ... Bareword found where operator expected at (eval 207) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 207) line 34, near "--82" (Missing operator before 82?) >> analog begin Bareword found where operator expected at (eval 208) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 208) line 34, near "--82" (Missing operator before 82?) >> @(regvar) Bareword found where operator expected at (eval 209) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 209) line 34, near "--82" (Missing operator before 82?) >> ; Bareword found where operator expected at (eval 210) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 210) line 34, near "--82" (Missing operator before 82?) >> ... Bareword found where operator expected at (eval 211) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 211) line 34, near "--82" (Missing operator before 82?) >> end Bareword found where operator expected at (eval 212) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 212) line 34, near "--82" (Missing operator before 82?) >> is not allowed if regvar is associated with the digital context. I Bareword found where operator expected at (eval 213) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 213) line 34, near "--82" (Missing operator before 82?) >> tried this with regvar being both a real number and a register. When Bareword found where operator expected at (eval 214) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 214) line 34, near "--82" (Missing operator before 82?) >> using a register I could replace it with "posedge regvar or negedge Bareword found where operator expected at (eval 215) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 215) line 34, near "--82" (Missing operator before 82?) >> regvar" and it worked). I believe support for this feature is implied Bareword found where operator expected at (eval 216) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 216) line 34, near "--82" (Missing operator before 82?) >> in the current LRM but not completely spelled out. It would be good Bareword found where operator expected at (eval 217) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 217) line 34, near "--82" (Missing operator before 82?) >> if we could clearly indicate that this was supported, and that regvar Bareword found where operator expected at (eval 218) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 218) line 34, near "--82" (Missing operator before 82?) >> is allowed to be a real variable associated with a digital context. Bareword found where operator expected at (eval 219) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 219) line 34, near "--82" (Missing operator before 82?) >> Bareword found where operator expected at (eval 220) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 220) line 34, near "--82" (Missing operator before 82?) > Bareword found where operator expected at (eval 221) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 221) line 34, near "--82" (Missing operator before 82?) > The latest merged syntax should make it clear that this type of event is Bareword found where operator expected at (eval 222) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 222) line 34, near "--82" (Missing operator before 82?) > allowed in the analog context. I also wish that Cadence Bareword found where operator expected at (eval 223) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 223) line 34, near "--82" (Missing operator before 82?) > implementation would support this type of event to. Bareword found where operator expected at (eval 224) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 224) line 34, near "--82" (Missing operator before 82?) > Bareword found where operator expected at (eval 225) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 225) line 34, near "--82" (Missing operator before 82?) >> 8. Currently $bitstoreal() et al is not supported within an analog Bareword found where operator expected at (eval 226) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 226) line 34, near "--82" (Missing operator before 82?) >> context. Bareword found where operator expected at (eval 227) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 227) line 34, near "--82" (Missing operator before 82?) >> Bareword found where operator expected at (eval 228) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 228) line 34, near "--82" (Missing operator before 82?) > Bareword found where operator expected at (eval 229) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 229) line 34, near "--82" (Missing operator before 82?) > Agreed. Bareword found where operator expected at (eval 230) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 230) line 34, near "--82" (Missing operator before 82?) > Bareword found where operator expected at (eval 231) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 231) line 34, near "--82" (Missing operator before 82?) >> 10. Finally, this is probably a longer term project, but we need to take Bareword found where operator expected at (eval 232) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 232) line 34, near "--82" (Missing operator before 82?) >> on the issue of making connect modules sensitive to power supplies, Bareword found where operator expected at (eval 233) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 233) line 34, near "--82" (Missing operator before 82?) >> particularly local power supplies. With the heavy emphasis on power Bareword found where operator expected at (eval 234) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 234) line 34, near "--82" (Missing operator before 82?) >> management, and the associated use of multiple power domains and the Bareword found where operator expected at (eval 235) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 235) line 34, near "--82" (Missing operator before 82?) >> disabling and enabling of power supplies, this is becoming Bareword found where operator expected at (eval 236) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 236) line 34, near "--82" (Missing operator before 82?) >> increasingly important. Bareword found where operator expected at (eval 237) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 237) line 34, near "--82" (Missing operator before 82?) >> Bareword found where operator expected at (eval 238) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 238) line 34, near "--82" (Missing operator before 82?) > Bareword found where operator expected at (eval 239) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 239) line 34, near "--82" (Missing operator before 82?) > Bareword found where operator expected at (eval 240) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 240) line 34, near "--82" (Missing operator before 82?) > I absolute agree. I have been regularly encountering similar problems in Bareword found where operator expected at (eval 241) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 241) line 34, near "--82" (Missing operator before 82?) > my work, the current work-around is tedious and results in slower Bareword found where operator expected at (eval 242) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 242) line 34, near "--82" (Missing operator before 82?) > simulations. Like Jonathan, I'll be happy to help define a solution to Bareword found where operator expected at (eval 243) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 243) line 34, near "--82" (Missing operator before 82?) > this problem. Bareword found where operator expected at (eval 244) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 244) line 34, near "--82" (Missing operator before 82?) > Bareword found where operator expected at (eval 245) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 245) line 34, near "--82" (Missing operator before 82?) > Regards Bareword found where operator expected at (eval 246) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 246) line 34, near "--82" (Missing operator before 82?) > Graham Bareword found where operator expected at (eval 247) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 247) line 34, near "--82" (Missing operator before 82?) > Bareword found where operator expected at (eval 248) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 248) line 34, near "--82" (Missing operator before 82?) > Bareword found where operator expected at (eval 249) line 34, near "--L386" (Missing operator before L386?) Number found where operator expected at (eval 249) line 34, near "--82" (Missing operator before 82?) >Received on Mon Jun 5 12:12:13 2006
This archive was generated by hypermail 2.1.8 : Mon Jun 05 2006 - 12:12:24 PDT