Problems? Is your data what you think it is? | |
PerlMonks |
Re^2: Converting VB to Perl,....and Visa Versaby gryphon (Abbot) |
on Sep 29, 2004 at 03:00 UTC ( [id://394835]=note: print w/replies, xml ) | Need Help?? |
Actually, VB has no more security holes than C#. They both get compiled to the CLR anyway. If there are any holes, it's in .NET, not VB. Personally, I dislike VB for the same reason someone mentioned in a previous post about translating VB to Perl but not the other way around. The whole point of a language is that it represents ideas. The easier it is to represent complex ideas, the better the language. (Yeah, yeah. I know. "What about speed," you ask? I say it's a secondary concern, IMHO. CPUs are far cheaper than dev hours. Just ask Classmates. They migrated their entire code-base from Perl to JSP a couple years ago, and they've been universally hating it.) VB can represent simple operations fairly well, but so can Perl. When you get into complex stuff, though, VB breaks down. I once tried to code in VB what took 1 line of Perl. I had to write two modules, define some classes and such, and add about 100 lines of code. It was an eye-openning experience. As a basic example, both VB and C# compile to more or less the exact same CLR code. However, it's easier to express ideas in C# than VB. (Why else do you suppose most .NET devs prefer C#?) Anyway, to answer the OP, I don't know of any VB-to-Perl translator. While it would be fairly simple for core VB, it would be a monumental task to deal with all the exceptions and add-ins. So why are you wanting a translator anyway? Do you need to port a legacy product from one language to the other? Do you need to embed Perl into VB, or VB into Perl? For the former, check with ActiveState. gryphon
In Section
Seekers of Perl Wisdom
|
|