User talk:Klever: Difference between revisions

From Rosetta Code
Content added Content deleted
(not really)
(Ambiguities and categorization.)
Line 3: Line 3:
::There aren't, really. Visual Basic 4/5/6 is a general-purpose implementation of VBA, while the VBA embedded in apps such as Word, Excel, etc is geared toward that specific app -- things like the <code>Document</code> object in MS Word and the <code>Spreadsheet</code> object in MS Excel. (Forms also work somewhat differently.) But VBA can do literally anything that VB6 can (except compile), and VB can do anything that VBA can do, and the code is ''almost'' identical.
::There aren't, really. Visual Basic 4/5/6 is a general-purpose implementation of VBA, while the VBA embedded in apps such as Word, Excel, etc is geared toward that specific app -- things like the <code>Document</code> object in MS Word and the <code>Spreadsheet</code> object in MS Excel. (Forms also work somewhat differently.) But VBA can do literally anything that VB6 can (except compile), and VB can do anything that VBA can do, and the code is ''almost'' identical.
::Most non-.Net VB code can be run from VBA with little or no changes, and vice-versa. -- [[User:Eriksiers|Erik Siers]] 20:19, 4 October 2011 (UTC)
::Most non-.Net VB code can be run from VBA with little or no changes, and vice-versa. -- [[User:Eriksiers|Erik Siers]] 20:19, 4 October 2011 (UTC)
:::Hm. This suggests a way to fix language categorization for VB and VB.Net. On one hand, you have Visual Basic.NET. On the other, you have Visual Basic for Applications. Categorization ambiguities between VB 4/5/6, VB.Net and VBA were a thorn in my side from nearly the very beginning of this site. That still leaves VB 1/2/3, though. (And I played with VB for DOS as a kid. I don't know where that fits) --[[User:Short Circuit|Michael Mol]] 13:57, 5 October 2011 (UTC)

Revision as of 13:57, 5 October 2011

I notice that you're using <lang VBA> for your VBA examples. Might I suggest using <lang vb> instead? Then the examples will get highlighted properly. (It's what I do.) -- Erik Siers 19:50, 4 October 2011 (UTC)

If there are significant differences between the languages it might be better to get VBA added to GeSHi. There are some instructions here. User:BenBE is our contact for the GeSHi project. If the languages aren't that different it's probably not worth it, but it may not be too difficult to get a language file set up (multiple users have done it before so I don't think it's too hard). --Mwn3d 20:06, 4 October 2011 (UTC)
There aren't, really. Visual Basic 4/5/6 is a general-purpose implementation of VBA, while the VBA embedded in apps such as Word, Excel, etc is geared toward that specific app -- things like the Document object in MS Word and the Spreadsheet object in MS Excel. (Forms also work somewhat differently.) But VBA can do literally anything that VB6 can (except compile), and VB can do anything that VBA can do, and the code is almost identical.
Most non-.Net VB code can be run from VBA with little or no changes, and vice-versa. -- Erik Siers 20:19, 4 October 2011 (UTC)
Hm. This suggests a way to fix language categorization for VB and VB.Net. On one hand, you have Visual Basic.NET. On the other, you have Visual Basic for Applications. Categorization ambiguities between VB 4/5/6, VB.Net and VBA were a thorn in my side from nearly the very beginning of this site. That still leaves VB 1/2/3, though. (And I played with VB for DOS as a kid. I don't know where that fits) --Michael Mol 13:57, 5 October 2011 (UTC)